Current published MarketCheck rate plans: per-call pricing, monthly quotas, and rate limits for a region, sourced from the live plan list (authoritative over docs). NA prices in USD, UK in GBP.
| Name | Required | Description | Default |
|---|---|---|---|
| region | No | Default NA. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate a safe read operation. The description adds useful context beyond that: data comes from a live plan list, is authoritative over docs, and currency is region-dependent (USD for NA, GBP for UK). No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one compact sentence that front-loads the core subject and packs in content, source, authority, and regional currency details without redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only lookup with no output schema, the description adequately covers what the tool returns, where the data comes from, and how region affects the result. Nothing essential is missing for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the single region parameter with an enum and default value. The description goes further by explaining the practical effect of the region choice on currency, adding meaning beyond the schema alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific resource ('MarketCheck rate plans') and enumerates what it returns: per-call pricing, monthly quotas, and rate limits. It also distinguishes itself from the documentation sibling tools by stating it is sourced from the live plan list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It clearly positions this tool as the authoritative live source over docs, so an agent knows to prefer it over get_doc_page or search_docs for current rate-plan information. It does not explicitly list alternatives, but the context is sufficient for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct role: semantic search, listing endpoints, fetching endpoint reference, fetching doc pages, and retrieving plan/limit info. get_doc_page and get_endpoint could seem close, but the descriptions clearly separate full pages from exact endpoint references.
All tool names follow a predictable verb_noun pattern in snake_case: get_doc_page, get_endpoint, get_plans_and_limits, list_endpoints, search_docs. The verbs vary by action but are semantically appropriate and consistent in style.
Five tools is well-scoped for a documentation server. Each tool covers a necessary access pattern without redundancy or bloat.
The set covers the full documentation workflow: semantic search over all docs, enumeration of endpoints, exact endpoint details, full page retrieval, and current plan/limit data. There are no obvious dead ends for common documentation queries.