Skip to main content
Glama
carbase-mcp

carbase-mcp

by vollebergh

get_fields

Retrieve specific specification fields for up to 20 vehicle versions and return each value, plus label suggestions when a requested field is unknown.

Instructions

A few specification fields for up to 20 versions, e.g. the step-in height of 10 cars.

fields: field labels as get_specs shows them, matched case-insensitively in any section, e.g. ["instaphoogte voor", "inhoud", "gewicht leeg"]. Returns per version its title and the value of each field (null when Carbase has none), plus unknown_fields with close label suggestions when a label exists in none of them. Much smaller than get_specs or compare_versions for this purpose.

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_ids": "<version_ids>",
      "fields": "<fields>"
    },
    "name": "get_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes
version_idsYes

Output Schema

NameRequiredDescriptionDefault
versionsYes
unknown_fieldsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations provided, so the description carries the burden. It discloses useful behavior beyond schema: case-insensitive matching across any section, null when Carbase has no value, and an unknown_fields response with close label suggestions. It does not mention permissions, rate limits, or ordering of results.

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?

Front-loads the purpose with a concrete example, then documents the fields parameter and the return shape. Mostly tight, though the fields explanation is slightly buried in a list-like block rather than organized as parameters.

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?

Output schema exists, so return values needn't be fully documented, but the description still explains the per-version title/value mapping and the unknown_fields edge case. Missing guidance on ID provenance and sibling routing keeps it from a 5.

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%, so the description must compensate, and it does explain the fields parameter format (labels as get_specs shows them, case-insensitive, with example values). The version_ids parameter is only implied by the stated limits (up to 20) and receives no explanation of where IDs come from.

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?

States a specific verb (get) and resource (specification fields) with scope: up to 20 versions and a limited field set. The example ("step-in height of 10 cars") makes the resource concrete, though it doesn't name a sibling explicitly for differentiation.

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?

Implies when to use it by stating it is "much smaller than get_specs or compare_versions for this purpose," which nudges the agent toward this tool when only a few fields are needed. It does not state exclusions like what get_specs should be used for instead.

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