Skip to main content
Glama

list_saved_vins

Read-only

List VINs saved by a user. Requires a user_token from /api/auth/login.

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>"
    },
    "name": "list_saved_vins"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_tokenYesJWT token from website login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact — that an authenticated user_token is required and where to get it — but says nothing about result volume, ordering, or what happens with an invalid/expired token.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the action front-loaded and the prerequisite following. Nothing could be removed without losing information.

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?

For a single-parameter, read-only listing tool with full schema coverage and complete annotations, this is nearly sufficient. The only residual gap is that it doesn't say whether results are scoped, paginated, or what a failure looks like, but those are minor for a tool of this simplicity.

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% and the schema already documents user_token as a JWT token from website login, so the description cannot add much. It contributes only the originating endpoint (/api/auth/login), which is marginally useful but not new semantic detail about the parameter's form or handling.

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 a specific verb and resource — 'List VINs saved by a user' — which is unambiguous and separable from save_vin/remove_saved_vin by implication. It stops short of explicitly naming the sibling it differs from, so it lands just below the top.

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?

It states a hard prerequisite (a user_token obtained from /api/auth/login), which tells the agent what it needs before calling. It offers no when-to-use vs. when-not-to-use guidance and no explicit routing to save_vin or remove_saved_vin.

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.