Skip to main content
Glama

update_user_profile

DestructiveIdempotent

Actualiza el perfil del usuario autenticado (nombre completo, descripción). No disponible para tokens sb_*.

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

Input Schema

NameRequiredDescriptionDefault
full_nameNoNombre completo
descriptionNoDescripción / bio del usuario

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds the auth constraint about sb_* tokens, which is context beyond the annotations. But with destructiveHint=true and zero required parameters, the critical behavior — whether omitted fields are preserved or cleared, and whether an empty call is a no-op or a wipe — is left unstated.

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 plus a short constraint, front-loaded with the action and resource. The field list in parentheses is mildly redundant with the schema but helps orient the reader quickly.

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 two-parameter self-profile mutation with no output schema and a declared auth restriction, the description covers what the tool touches and who can call it. The remaining gap is partial-update semantics for a tool with no required parameters.

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 description coverage is 100%, so the schema already documents both properties. The description restates them in the parenthetical without adding format, length, or optionality semantics, so baseline 3 applies.

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: updates the authenticated user's own profile, and names the updatable fields (full name, description). It clearly cannot be confused with update_workspace or update_document, though it never explicitly contrasts itself with the sibling get_user_profile.

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?

Provides one real precondition — unavailable for sb_* tokens — which is genuine usage guidance. However, there is no statement of when to prefer this tool over siblings or what to do instead when the token restriction applies, leaving usage largely implied.

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.

Resources