Skip to main content
Glama

Users Show

users_show

Fetch details of the authenticated user and pass optional query fields to tailor the returned user data.

Instructions

Get details of the authenticated user. GET /user

query keys (fields[users]) pass through verbatim.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "users_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose behavior via the raw endpoint (GET /user) and the pass-through semantics of query keys, which signals a read-only retrieval and how query arguments are forwarded. It omits authentication requirements, error behavior, and what the response actually contains.

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?

Two short sentences, front-loaded with the purpose before the parameter note. No filler, though the terse 'pass through verbatim' phrasing and inline backtick markup make it slightly cryptic on first read.

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 with no annotations and no output schema, the definition covers purpose and query forwarding but never indicates what a user detail payload includes or how the sparse-fieldset query alters it. Adequate for invocation, incomplete for interpreting the result.

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

Parameters4/5

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

The single query parameter has 0% schema description coverage, so the description must compensate. It does so by explaining the pass-through contract and naming the concrete fields[users] key family, which is meaningfully more than the schema's bare additionalProperties: string. It stops short of documenting other likely key names or value formats.

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 and resource: 'Get details of the authenticated user', with the backing endpoint GET /user. This clearly distinguishes it from resource-specific siblings like organisations_show or letters_show, since it names 'authenticated user' as the target rather than an ID-supplied entity.

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?

The phrase 'the authenticated user' implicitly tells the agent no user identifier is passed, which is useful scoping. However, it gives no explicit when-to-use guidance, no statement about when to prefer other tools, and no prerequisites such as required auth scopes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.