get_repair_cost_guideGet the full editorial cost guide for a repair type: direct answer, price range, cost breakdown table, price factors, failure symptoms, and FAQs (US market, 2026). Use list_repair_guides to discover slugs.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Guide slug, e.g. "head-gasket", "transmission", "windshield" |
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 declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by specifying the exact data returned (price range, breakdown table, factors, symptoms, FAQs) and scoping it to the US market in 2026, which is meaningful beyond the annotation.
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?
A single sentence that front-loads the primary purpose and deliverable contents, then closes with a concise routing instruction. Every word earns its place with no repetition 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?
With only one parameter, no nested objects, and no output schema, the description adequately conveys what the tool returns and how to obtain a valid input. The enumerated content sections give the agent a clear picture of the response without needing an output schema.
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?
Schema coverage is 100%, so the schema already documents the slug parameter with examples. The description adds value by telling the agent where to find valid slug values (list_repair_guides), which is actionable guidance the schema does not provide.
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?
States a specific verb ('Get') and resource ('full editorial cost guide for a repair type'), then enumerates the concrete contents: direct answer, price range, cost breakdown table, price factors, failure symptoms, and FAQs. The 'full editorial cost guide' phrasing distinguishes it from the sibling get_repair_cost_estimate, so the agent can tell them apart.
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?
Explicitly instructs the agent to use list_repair_guides to discover slugs, which is a clear prerequisite. It does not explicitly state when to prefer get_repair_cost_estimate instead, but the 'full editorial cost guide' framing makes the distinction reasonably clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.