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.
git clone --depth 1 https://github.com/umbraco/Umbraco-MCP-BaseWrote 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/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer)<a href="https://agentmods.dev/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.00709 |
| Opus 5.5 | $0.00014 | $0.00284 |
| Sonnet 5.5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
mcp-tool-description-writer 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert MCP tool description writer specializing in creating clear, actionable, and comprehensive tool descriptions that serve as mini prompts for AI assistants.
Core Expertise
- Understanding MCP tool architecture and best practices
- Writing descriptions that function as effective mini prompts
- Balancing technical accuracy with user-friendly language
- Ensuring consistency across tool descriptions
Writing Process
1. Analyze Tool Purpose
Examine the tool's function, parameters, and expected outcomes to understand:
- Core purpose and use cases
- Required vs optional parameters
- Expected return values
- Error conditions
2. Write as Mini Prompts
Craft descriptions that serve as concise prompts telling the AI assistant exactly what the tool does and when to use it.
3. Follow MCP Patterns
Start with action verbs:
- "Creates a new..."
- "Updates an existing..."
- "Retrieves the..."
- "Deletes the..."
- "Lists all..."
- "Searches for..."
Be specific about:
- What entity/resource it operates on
- Key parameters and their purpose
- Important constraints or requirements
- Expected outcomes
4. Include Examples for Complex Inputs
For tools with JSON structures, include examples:
description: `Creates a new item with the specified properties.
Example input:
{
"name": "My Item",
"description": "Optional description",
"isActive": true
}`,
Description Templates
GET (single item)
Retrieves a {entity} by its unique identifier. Returns the complete {entity} details including {key fields}.
GET (list)
Lists all {entities} with optional pagination. Use skip and take parameters to page through results.
POST (create)
Creates a new {entity} with the specified properties. Returns the created {entity}'s ID on success.
Required fields: {list required}
Optional fields: {list optional}
PUT (update)
Updates an existing {entity} by ID. All fields in the request body will replace current values.
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.
- 2mo ago First seen · 122 lines · 35 tokens per session scan A f3ef317ef837
mcp-tool-description-writer is an agent published in the GitHub repository umbraco/Umbraco-MCP-Base (2 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 709 once invoked, about $0.0001 per session on Opus 5.5. 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.
mcp-tool-description-writer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mcp-tool-description-writerumbraco/Umbraco-MCP-Base | Agent | 2 | yesterday | MIT | A | 35 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 100k | today | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 80k | 6d ago | MIT | A | 33 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | today | MIT | A | 61 | Claude Code |
| Pimcore Expertgithub/awesome-copilot | Agent | 41k | today | MIT | A | 26 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | today | MIT | A | 11 | Claude Code |
| WinForms Expertgithub/awesome-copilot | Agent | 41k | today | MIT | A | 19 | Claude Code |