Skip to main content
Glama

vehicle_emissions

Read-only

Get EPA emissions for an explicit EPA vehicle ID.

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": "vehicle_emissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 and external-data nature are covered structurally. The description adds essentially nothing beyond those hints: no indication of which emissions data is returned (year, model, test results), what happens when the ID is unknown, or whether the lookup can fail or be rate-limited.

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 action front-loaded and no filler. The repeated "EPA ... EPA" phrasing is slightly redundant but harmless; the brevity reflects under-specification rather than waste.

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

Completeness2/5

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

This is a simple read-only lookup with no output schema, so the description is the only place to learn what comes back. For a tool whose entire value is the returned emissions dataset, it omits return content, ID provenance, and failure behavior, leaving the agent to guess.

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

Parameters2/5

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

Schema coverage is 0% – the single `id` property is typed as a plain string with no documentation. The description does add that the value must be an EPA vehicle ID rather than a VIN, but it gives no format, example, or guidance on obtaining one, which leaves the only parameter substantially under-specified.

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?

The description names a specific verb and resource ("Get EPA emissions") and narrows the input to "an explicit EPA vehicle ID," which distinguishes it from VIN-oriented siblings like decode_vin. It stops short of naming another tool or explaining how it differs from epa_vehicle or vehicle_dimensions, so it is clear but not sibling-differentiating.

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

Usage Guidelines3/5

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

"Explicit EPA vehicle ID" implies the caller must already have an EPA ID rather than a VIN, which implicitly routes agents away from the VIN-decoding siblings. However, there is no explicit when-to-use statement, no mention of where such an ID comes from (e.g., from epa_vehicle), and no exclusions.

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.