Skip to main content
Glama

get_output_preferences

Get the user's VIN report output preferences.

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

Input Schema

NameRequiredDescriptionDefault
user_tokenYesJWT token

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 declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, but the description adds nothing beyond the one-line purpose. It does not say what happens when the user has no saved preferences (defaults? empty?), whether authentication scope matters beyond the token, or whether the call has any side effects. There is a mild tension between a "get" verb and readOnlyHint=false that the description never reconciles, though a non-read-only default is common enough that this is not a hard contradiction.

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 short sentence with zero filler and the key noun front-loaded. It is appropriately sized for a trivial single-parameter lookup, though it is terse to the point of omitting anything the agent could act on.

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 one-parameter read tool with no output schema, the description covers what the tool is but not what comes back or how to interpret an empty result. It is minimally adequate given the low complexity, but an agent still cannot predict the response shape from the definition alone.

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?

Only one parameter (user_token) exists and the schema documents it fully at 100% coverage, so the baseline is 3. The description adds no meaning about token scope, whose preferences are read, or any authorization requirement beyond the schema's "JWT token".

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?

"Get the user's VIN report output preferences" gives a specific verb (get) and a specific resource (VIN report output preferences), so the agent knows exactly what is returned. It implicitly contrasts with the sibling update_output_preferences through the verb, but neither that sibling nor the read/write split is stated explicitly.

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 mention of when to prefer this over update_output_preferences, and no prerequisite or exclusion noted. The agent must infer from the verb alone that this is the retrieval counterpart to the update tool.

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.