Skip to main content
Glama

remove_saved_vin

Destructive

Remove a VIN from the user's saved collection.

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": "remove_saved_vin"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesVIN to remove
user_tokenYesJWT token from website login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds only a scoping phrase ('the user's saved collection') and omits behavior that matters for a destructive call: whether removal is idempotent, whether it errors on a non-saved VIN, and whether the change is reversible.

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 no filler or repetition. It is perhaps too terse given the destructive nature of the operation, but there is no wasted wording.

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 simple two-parameter destructive tool with full schema coverage and annotations carrying the safety hints, the definition is minimally sufficient. It still leaves the agent guessing about error behavior and preconditions, which is a real gap for a removal 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 coverage is 100%, with both vin and user_token individually described ('VIN to remove', 'JWT token from website login'), so the baseline is 3. The description adds nothing about token acquisition or VIN format handling beyond what the schema already provides.

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 supplies a specific verb ('Remove') and resource ('a VIN from the user's saved collection'), which is enough to distinguish it from siblings like save_vin or list_saved_vins. It stops short of explicitly naming those siblings, so the differentiation is inferable rather than stated.

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 when-to-use guidance, no prerequisite (such as obtaining a user_token via login or looking up a VIN with list_saved_vins first), and no statement of what to do if the VIN is not currently saved. The agent must infer all of this from the tool name alone.

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.