Skip to main content
Glama

vehicle_dimensions

Read-only

Canadian model-variant dimensions in cm and kg. Not VIN-specific.

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": {
      "year": "<year>",
      "make": "<make>",
      "model": "<model>"
    },
    "name": "vehicle_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYes
yearYes
modelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 useful scope context — Canadian-market variants only, metric units — but says nothing about what happens for unknown or non-Canadian year/make/model combinations, or whether the result is a partial match.

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?

Two tight sentences with the scope constraint front-loaded; nothing extraneous. The brevity is appropriate, but the second sentence fragment is a negative constraint rather than a positive usage cue.

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?

For a lookup requiring three mandatory identity parameters with zero schema descriptions and no output schema, the description is too thin. It never describes the shape of the returned dimensions or how mismatches/ambiguity in year-make-model are handled.

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 description coverage is 0%, so the description carries the full burden for year, make, and model, and it adds nothing about them. It does not explain format expectations, whether make/model must match Canadian catalog names, or what happens with an unlisted year.

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 the resource precisely — model-variant dimensions — and adds the unit conventions (cm and kg) plus the market scope (Canadian). The "Not VIN-specific" clause distinguishes it from decode_vin and validate_vin, though no explicit verb like "look up" is used.

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?

The single phrase "Not VIN-specific" implicitly routes agents to VIN-based siblings when they have a VIN, which is genuine guidance. However, it never states positively when to use this tool (e.g., when only year/make/model are known) nor mentions related siblings like vehicle_catalog or compare_vehicles.

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.