Skip to main content
Glama

Update User

update_user

Updates a user's first name, last name, nickname, or institution and returns the previous values; email and global role changes are not supported.

Instructions

(Admin) Cambia nombre, apellido, nickname o institución de un usuario. Devuelve los valores previos.

La API no permite cambiar email ni rol global.

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

Input Schema

NameRequiredDescriptionDefault
user_idYes
nicknameNo
last_nameNo
first_nameNo
institution_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes beyond them by disclosing the admin authorization requirement, the partial-update scope, and that the previous values are returned. It does not address whether passing null clears a field or leaves it untouched, which matters given every optional parameter defaults to null.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and the admin gate, followed by the return-value and limitation notes. Every clause carries information; nothing is redundant with the title.

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?

An output schema exists and the description still helpfully notes that prior values are returned, so return shape is covered. For a mutation tool the remaining gap is the null-handling of the four optional fields, which an agent must know to avoid accidentally clearing data.

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?

Schema description coverage is 0%, so the description carries the whole burden, and it names the four optional fields (nickname, first_name, last_name, institution_id) in business terms. The required user_id is left unexplained and no format details are given, and the null-versus-omit semantics of the nullable defaults remain ambiguous.

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?

Uses a specific verb ("Cambia") with a specific resource ("usuario") and enumerates the mutable fields (nombre, apellido, nickname, institución), plus a scope qualifier "(Admin)". It stops short of naming a sibling, but the explicit statement of which fields cannot be changed already separates it from write tools like set_user_password or create_users.

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 implies a privilege prerequisite and the last sentence rules out email and global role changes, which is useful negative guidance. However, it never says when to reach for this tool versus a sibling such as set_user_password or grant_course_role, so the routing guidance remains implicit.

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