Skip to main content
Glama

owner_reported_mpg

Read-only

Voluntary owner-reported MPG for an EPA configuration, including sample size and limitations.

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": {
      "id": "<id>"
    },
    "name": "owner_reported_mpg"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing data provenance (owner-submitted, voluntary) and that results carry sample size and limitations, which tells the agent to treat outputs as estimates. It does not say what happens when no reports exist for a configuration.

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

Conciseness4/5

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

A single tight sentence with the resource and its caveats front-loaded and no filler. It is efficient, though the terseness leaves key details (identifier type, no-data behavior) unstated.

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

Completeness3/5

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

With only one parameter, annotations covering safety, and no output schema, the description does enough to set expectations about returned content (sample size, limitations). It falls short on identifying what 'id' refers to and on behavior when no owner reports are available.

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 coverage is 0% for the single required 'id' parameter, so the description must compensate. Saying the data is 'for an EPA configuration' hints the id is an EPA configuration identifier rather than a VIN, but it never states the identifier type or format explicitly, leaving ambiguity given siblings like decode_vin and epa_vehicle.

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

Purpose4/5

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

Names a specific resource with scope: voluntary owner-reported MPG data for an EPA configuration, plus what the payload includes (sample size, limitations). It is clearly distinct from catalog/decoding siblings, though it does not explicitly contrast itself with the EPA-rating tool.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The words 'voluntary' and 'limitations' imply the data is anecdotal rather than official, but the agent must infer that this is for real-world mileage checks versus an EPA-rating lookup.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.