Skip to main content
Glama

save_vin

Save a VIN to a user's collection with an optional label.

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": {
      "user_token": "<user_token>",
      "vin": "<vin>"
    },
    "name": "save_vin"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYes17-character VIN to save
labelNoCustom label (e.g. "Dad's truck")
user_tokenYesJWT token from website login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive write (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the safety profile is covered. The description adds that the write targets a per-user collection and that the label is optional, but says nothing about duplicate handling if the VIN already exists or what the call returns.

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 zero filler; the core action leads. It is efficient but so terse that the remaining sentences that would earn their place are simply absent.

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 three fully documented parameters and no output schema, most of the calling burden is carried by the schema and annotations. Still missing are duplicates/overwrite behavior and any hint of the response, which matter for a persistence operation.

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%, so the schema already documents vin, label, and user_token including the 17-character constraint and JWT source. The description only echoes that the label is optional, adding no meaning beyond the structured fields — baseline 3.

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 (save) plus resource (VIN) and target (user's collection), which is enough to separate it from siblings like remove_saved_vin and list_saved_vins. It stops short of naming an alternative, but the purpose itself 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?

The description only implies usage; it never says when to call this versus decode_vin, validate_vin, or list_saved_vins, nor whether the VIN should be validated first. No prerequisites, exclusions, or alternatives are given.

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.