Skip to main content
Glama

get_user

Read-onlyIdempotent

Retrieve a single user's profile with their post total and open versus completed todo counts. Use the user ID from list_users to look up the right record.

Instructions

Show one user's profile with their number of posts and open/completed todos.

    Get user_id from list_users.
    

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_id": "<user_id>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesnumeric user id from list_users

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?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds value by disclosing which fields come back (post count, open/completed todo counts), but says nothing about what happens for missing or deleted users, permissions, or error behavior.

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 and followed by the one prerequisite an agent needs. Slightly wasteful indentation/whitespace and a redundant restatement of the user_id sourcing keep it from being maximally tight.

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 tool with no output schema, the description covers what it does, what it returns, and where the id comes from. The remaining gaps (error/missing-user handling) are minor for a simple idempotent read.

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 parameter already documents itself as the "numeric user id from list_users," which the description merely repeats via the provenance hint. No extra meaning about id semantics, validity or reuse is added beyond the schema.

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 ("Show one user's profile") and scopes it to a single user, which clearly separates it from the list-style sibling list_users. It also previews the payload (post count, open/completed todos), though it never explicitly contrasts itself with siblings like search_posts.

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 line "Get user_id from list_users" gives a concrete prerequisite and implies the tool is for single-user lookups, but there is no explicit when-to-use/when-not-to-use guidance or stated alternative for bulk or search-style retrieval.

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

Deploy Server

Other Tools