Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/kontent-ai/mcp-server/mcp-tool-naminggit clone --depth 1 https://github.com/kontent-ai/mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/kontent-ai/mcp-server/mcp-tool-naming)<a href="https://agentmods.dev/rules/kontent-ai/mcp-server/mcp-tool-naming"><img src="https://agentmods.dev/badge/rules/kontent-ai/mcp-server/mcp-tool-naming.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00135 |
| Opus 5 | $0.00000 | $0.00068 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
mcp-tool-naming scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
When creating or modifying MCP tools, follow these naming conventions:
- Format:
[action]-[entity] - Use full entity names:
content-type,content-type-snippet,content-item,content-item-variant,taxonomy-group - For list tools filtered by another entity:
list-[entity]-by-[filter-entity](e.g.,list-content-item-variants-by-collection) - Examples:
get-content-type,list-content-item-variants,patch-content-type-snippet
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 12 lines · 0 tokens per session scan A 9ffc8860bbe1
mcp-tool-naming is a cursor rule published in the GitHub repository kontent-ai/mcp-server (9 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 135 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
cursorrules
Robot control server. Do not move the physical robot without checking health first.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
cursor_rules
Guidelines for creating and maintaining Cursor rules to ensure consistency and effectiveness.