Skip to main content
Glama

get_user_profile

Read-onlyIdempotent

Obtiene el perfil del usuario autenticado (id, email, full_name, avatar_url, description). Solo funciona con JWTs de usuario — NOT disponible para tokens sb_* (esos son tokens de workspace, no de usuario). Retorna también first_name y last_name derivados.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds non-obvious behavioral context the annotations cannot express: the authentication requirement (user JWT vs. sb_* workspace token) and the fact that first_name/last_name are derived rather than stored fields.

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?

Three short sentences, each carrying distinct information: what is returned, the auth constraint, and the derived fields. The auth restriction is front-loaded right after the purpose statement with no filler.

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?

There is no output schema, so the description's enumeration of return fields (id, email, full_name, avatar_url, description, plus derived first_name/last_name) carries the return-value burden and does so adequately. What is missing is only a note on failure behavior when an sb_* token is used or on how to fall back, which is minor for a zero-argument read tool.

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 tool takes zero parameters, so there is nothing for the schema to document and nothing the description needs to compensate for. Baseline for a 0-param tool applies; no parameter-level semantics are required.

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 ('Obtiene el perfil del usuario autenticado') and enumerates the returned fields, so the agent knows exactly what it gets. It does not, however, distinguish itself from plausible look-alikes in the sibling list such as get_me, leaving a small ambiguity about which 'my profile' tool to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a concrete eligibility condition: it only works with user JWTs and is not available for sb_* workspace tokens. That is real when-to-use guidance and steers the agent away from a guaranteed failure, though it names no alternative tool to use instead for workspace tokens.

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