Skip to main content
Glama

J.C. Lewis Auto Group

check_availability

Check availability and pricing for multiple VINs (up to 50).

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": {
      "vins": "<vins>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden and delivers almost nothing beyond the cap: no statement about pagination or batching behavior above 50, what happens when a VIN is unknown or a vehicle is unavailable, whether partial results are returned, or any rate/auth constraints. Only the 50-item limit is new behavioral information.

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?

A single front-loaded sentence with the resource first and the constraint last; nothing is wasted. It is arguably too terse for a tool with zero annotations, but that is a completeness issue rather than verbosity.

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?

An output schema exists, so return values need not be described, and the input cap is given. However, for a no-annotation tool with an undocumented parameter, missing detail on partial failures, unknown VINs, and batching above 50 leaves real gaps an agent would want covered.

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 0%, so the description must compensate; it does partially by establishing that 'vins' is a list of VINs with a hard maximum of 50. It adds no format or validation detail (VIN length, case, duplicate handling) beyond that, so the single parameter is only half-specified.

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 concrete verb plus two resources (availability and pricing) and a batched scope ('multiple VINs, up to 50'). That batch framing distinguishes it from single-VIN siblings like get_vehicle_by_vin or decode_trade_in_vin, though it never names them explicitly.

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 batch nature and the 50-VIN ceiling imply when to reach for it (bulk lookups on a list of VINs), but there is no explicit when-to-use/when-not guidance and no mention of the single-VIN alternatives in the sibling set. Usage is inferable rather than stated.

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