Borrowing it
Nothing to install: this file belongs to Grinv/tmdb-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Grinv/tmdb-mcp/main/.agents/skills/tool-description-check/SKILL.mdgit clone --depth 1 https://github.com/Grinv/tmdb-mcpWrote 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/skills/grinv/tmdb-mcp/tool-description-check)<a href="https://agentmods.dev/skills/grinv/tmdb-mcp/tool-description-check"><img src="https://agentmods.dev/badge/skills/grinv/tmdb-mcp/tool-description-check.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.1 | $0.00086 | $0.03492 |
| Opus 5 | $0.00043 | $0.01746 |
| Sonnet 5 | $0.00017 | $0.00698 |
| Haiku 4.5 | $0.00009 | $0.00349 |
Grade A, and why
tool-description-check 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 7d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tool descriptions: what to check before committing
Published research on this exact failure mode: Glama's TDQS methodology found 97% of 856 tools across 103 real MCP servers have a description defect — 56% don't clearly state what the tool does, 89% don't say when to use it. Separately, "From Docs to Descriptions" measured that strong descriptions get 260% more selection in competitive scenarios and lift task success ~6 points. Bad descriptions aren't a hypothetical risk; they're the median case. This server is scored on the same rubric at glama.ai/mcp/servers/Grinv/tmdb-mcp/score (re-analyzed on Glama's own schedule, not on push — treat this as a manual pre-commit check, not something to verify live after every edit).
| TDQS dimension | Weight | Question |
|---|---|---|
| Purpose Clarity | 25% | Does the description state what the tool does? |
| Usage Guidelines | 20% | Does it say when to use this tool vs. alternatives? |
| Behavioral Transparency | 20% | Does it disclose behavior beyond what annotations already provide? |
| Parameter Semantics | 15% | Does it add meaning beyond what the input schema provides? |
| Conciseness & Structure | 10% | Is it appropriately sized and front-loaded? |
| Contextual Completeness | 10% | Given the tool's complexity, is the description complete enough? |
Usage Guidelines and Behavioral Transparency carry the most weight after Purpose Clarity — double-check those two first on any new or edited tool.
Two rules that override everything below
- No unverified claims. Every behavioral statement in a description —
not just "the schema allows this input," which is self-evidently true,
but "here's what happens when you send it" — must be backed by one of:
- an in-code comment that already documents a verified-live upstream
quirk, cited by reference instead of re-asserted from memory (e.g. the
verified live against the real /discover/tvcomment abovecertification/TV_TYPES/TV_STATUSESinsrc/tools/tmdb/discover.ts), or an existing note in docs/architecture.md or docs/clients.md; - a fresh live call against the real TMDB/OMDb API made during this review, with the actual response observed;
- direct reading of the exact function implementing the behavior, when
it's deterministic code logic (e.g.
getEnrichedDetail's ratings fallback insrc/tools/tmdb/details.ts) rather than an external API's quirk.
- an in-code comment that already documents a verified-live upstream
quirk, cited by reference instead of re-asserted from memory (e.g. the
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.
- 7d ago First seen · 239 lines · 86 tokens per session scan A e196881d5642
tool-description-check is a skill published in the GitHub repository Grinv/tmdb-mcp (4 stars, last pushed 13d ago), licensed MIT. It adds 86 tokens to every session and 3,492 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
tool-description-check
Self-check a new or edited MCP tool description/field .describe() text before committing — verify every behavioral claim against live testing or source, check for contradictions with sibling tools, and score against Glama's Tool Definition Quality Score (TDQS) rubric. Use whenever a tool description or schema field…
liveagent-code-review
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.
prompt-check
Live-test every MCP Prompt in src/tools/prompts.ts through the real MCP protocol (not a static read) across every argument combination. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.
release
Cut a release of steam-games-mcp — draft CHANGELOG entries, check docs/metadata consistency, then bump/tag/push. Use when asked to release, cut a version, or publish a new version of this package.
docs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.