Skip to main content
Glama

Ask Bestie Cars

Car model registration history

get_product
Read-onlyIdempotent

A model group's registration ranks and share history. Includes current SEK retail and separate private/business lease observations where verified, with sources and contract terms.

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": {
      "product": "<product>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoSE only. See pricing for current verified SEK retail/private/business lease observations.
productYesProduct id or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered and the description does not contradict it. The description does add value beyond annotations by disclosing return content — verified SEK retail plus separate private/business lease observations, with sources and contract terms. It stops short of saying what happens when no verified observation exists or how history depth is bounded.

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 sentences, no filler, and the core resource statement comes first. The second sentence is dense and packs three separate ideas (retail, lease split, sources/terms), which slightly hurts scannability but nothing is wasted.

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 two parameters, full schema coverage, and no output schema, the description does enough to convey what the result contains, which is its main burden here. The gaps are on the selection side — no guidance distinguishing it from ranking-family siblings — and no note on what happens when verified data is unavailable.

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 100%, and the schema's own region description already states 'SE only' and points to pricing for verified SEK retail/private/business lease observations. The description restates that same lease/retail framing without adding syntax, format, or id-resolution detail for the required 'product' parameter. Baseline 3 applies since the schema carries the semantics.

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

Purpose3/5

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

The description names a specific resource — a model group's registration ranks and share history — but is a bare noun phrase with no verb, so what the tool actually does (retrieve? list? compute?) is inferred. It also offers no differentiation from siblings like get_ranking or trending, which sound like they cover overlapping ground.

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 when-to-use guidance at all: no statement of when this tool is the right choice, no exclusions, and no mention of alternatives such as get_ranking or trending. The only guidance-shaped content ('where verified') describes data quality, not invocation conditions.

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.

Resources