Skip to main content
Glama

Get User

get_user
Read-only

Retrieves a user's profile details, role, tags, and course roles by user ID for administrative review.

Instructions

(Admin) Detalle de un usuario: datos, rol, tags y roles de curso.

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_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the admin-only access constraint, which is genuine value beyond the annotations, but says nothing about behavior on missing/invalid users or permission failures.

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 compact sentence with the access constraint front-loaded and the returned fields listed efficiently. No wasted wording, though the Spanish phrasing is terse to the point of being slightly clipped.

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?

An output schema exists, so return values need not be explained, and the tool is simple with one parameter. Still, the admin constraint and the user_id semantics are the only behavioral facts given, leaving the definition adequate but thin for a lookup tool.

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?

There is a single required parameter (user_id) with 0% schema description coverage, so the description must compensate. 'Detalle de un usuario' implies the parameter identifies the user, but it never states the expected format or whether it is an internal ID versus another identifier.

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 ('Detalle') and resource ('un usuario') and enumerates the returned facets (datos, rol, tags, roles de curso), which distinguishes it from siblings like update_user or find_users. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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 '(Admin)' prefix signals a prerequisite audience, which is useful context for when the tool is callable. However, there is no guidance on when to use this versus find_users (search) or update_user (mutation), leaving the agent to infer the boundary.

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