Skip to main content
Glama

update_output_preferences

Update which sections appear in VIN reports.

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

Input Schema

NameRequiredDescriptionDefault
user_tokenYesJWT token
show_engineNo
show_photosNo
show_recallsNo
show_overviewNo
show_raw_nhtsaNo
show_complaintsNo
show_fuel_economyNo
show_safety_ratingsNo
show_safety_equipmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false with destructiveHint=false, so the safety profile is known. Beyond that, the description says nothing about whether omitted booleans are left unchanged or reset to defaults, which is the key behavioral question for a 9-flag preference mutation.

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

Conciseness3/5

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

A single short sentence with no wasted words, but it is under-specified rather than concise, since a 10-parameter mutation tool warrants more explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with nine undocumented boolean flags and no output schema, the description leaves the semantics of partial updates and the effect on unspecified sections entirely unstated. An agent could easily call it with the wrong expectation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 10% — only user_token carries a description ('JWT token'), and the nine show_* booleans are undocumented in both schema and description. Their names are self-explanatory, but the description adds no meaning about defaults, tri-state semantics, or how they map to report sections.

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 (update) and resource (sections shown in VIN reports), which clearly separates it from the read-side sibling get_output_preferences implied by its name. It is clear but does not explicitly call out that counterpart.

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 guidance on when to use this versus get_output_preferences, no note about prerequisites such as authentication, and no statement about whether partial updates are allowed. The agent must infer all of this.

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.