Skip to main content
Glama
carbase-mcp

carbase-mcp

by vollebergh

list_models

Retrieve all models for a specified car brand, including each model's slug, name, and version count.

Instructions

All models of a brand: slug, name and number of versions.

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": {
      "brand": "<brand>"
    },
    "name": "list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand slug from list_brands, e.g. 'volkswagen'

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing behavioral. It implies a read-only bulk listing ('All models of a brand'), but says nothing about ordering, pagination, empty-result behavior, or what happens with an invalid brand slug.

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?

One short, front-loaded sentence with zero filler. The field list after the colon is mildly redundant with the output schema, but it costs almost nothing and does orient the agent quickly.

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?

For a single-required-parameter read tool with an output schema and full schema coverage, the description is sufficient to attempt a correct call. It is thin on edge cases (unknown brand, result ordering) but nothing critical to invocation is missing.

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 description coverage is 100% and the single 'brand' parameter is already documented with an example ('volkswagen') and its source tool. The description adds no meaning beyond that, so the baseline 3 applies.

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 the resource (models) and the scoping key (of a brand), so an agent can tell it apart from list_brands and compare_versions without opening the schema. It is telegraphic rather than verb-led, but the list intent is unambiguous.

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 explicit when-to-use or when-not-to-use guidance, and no sibling alternative is named in the description itself. The only routing hint ('Brand slug from list_brands') lives in the schema parameter text, not here.

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