Skip to main content
Glama
Sign In

pricemyrepair-mcp

by io.github.iwanek86
OverviewDiscussionsAdmin

get_model_costs

Get the full table of typical UK repair and servicing costs (GBP) for one car model from PriceMyRepair — every repair the price matrix covers, in one call. Use when the user asks what a particular car costs to maintain or repair in general.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model": "<model>"
    },
    "name": "get_model_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesCar model, e.g. "Ford Focus". Use "uk-average" for a generic figure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful traits: it returns the full table, covers every repair in the price matrix, uses GBP, and is a single-call operation. However, it does not describe the output format, error behavior, or any access requirements, leaving some ambiguity for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no wasted words. The primary purpose is front-loaded, and the usage guidance is included without bloat, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool, the description covers the essential context: what data is returned, the currency/region, the scope ('every repair'), and the general use case. It does not describe the return structure, but given the low parameter complexity and the schema's completeness, this is only a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the sole parameter 'model' is already well-documented with an example and the 'uk-average' special value. The description adds mild context by saying the costs are 'for one car model', but it does not meaningfully extend the parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Get the full table'), a precise resource ('typical UK repair and servicing costs (GBP) for one car model'), and a distinguishing scope ('every repair the price matrix covers, in one call'). This makes it easy to tell apart from the sibling get_repair_cost, which presumably returns a single repair cost.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use the tool: 'when the user asks what a particular car costs to maintain or repair in general.' This provides clear context, though it does not explicitly name sibling tools or state when not to use it, so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pricemyrepair-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources