Skip to main content
Glama
carbase-mcp

carbase-mcp

by vollebergh

get_specs

Retrieve full specifications for one car version by ID, grouped by section; filter sections to focus on the data you need.

Instructions

Full specifications of one version (id from search), grouped per section, Dutch labels.

Sections: BASISKENMERKEN (prices), MOTORISERING, BRANDSTOFMOTOR or ELEKTROMOTOR/ACCU, PRESTATIES, VERBRUIK (WLTP), ONDERSTEL, GEWICHTEN, BAGAGE/LAADRUIMTE, EXTERIEURMATEN, INTERIEURMATEN (incl. instaphoogte), VEILIGHEID, COMFORT, INTERIEUR, EXTERIEUR, SERVICE & GARANTIE, HISTORISCHE NIEUWPRIJZEN.

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": {
      "version_id": "<version_id>"
    },
    "name": "get_specs"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionsNoSection names to keep, e.g. ['PRESTATIES']
version_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
specsYes
titleYes
subtitleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: results are grouped per section, labels are Dutch, and the exact section taxonomy is enumerated. It does not explicitly state read-only/no side effects, but "get" plus the enumerated static taxonomy makes the read nature unambiguous.

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?

Front-loaded one-sentence summary followed by a compact section list that doubles as the filter vocabulary. No filler; every line is usable by the caller.

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?

An output schema exists, so return values need not be described, and the description still adds grouping and language context. The only gap is the absence of any note on response size or whether all sections are returned when the filter is omitted.

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

Parameters4/5

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

Schema coverage is only 50%: version_id has no schema description, and the description compensates by explaining it is an id obtained from search. The enumerated section names (BASISKENMERKEN, MOTORISERING, ...) are exactly the vocabulary the sections filter accepts, adding real meaning beyond the schema's single example ['PRESTATIES'].

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?

States a specific verb and resource ("Full specifications of one version") plus the output shape (grouped per section, Dutch labels) and where the identifier comes from ("id from search"). An agent can distinguish this from search/compare_versions without opening any schema.

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?

The parenthetical "id from search" gives the prerequisite and routes the agent to the sibling that produces the required version_id. It does not state when to prefer compare_versions or get_fields instead, so it stops short of full alternative guidance.

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