get_my_profileRetrieve the authenticated user's profile, scopes, and optional permissions. Use it to verify access rights or create a default scope if none exists.
Devuelve el perfil del usuario autenticado, sus scopes y (opcionalmente) permisos.
| Name | Required | Description | Default |
|---|---|---|---|
| createDefaultScope | No | Crear scope por defecto si no tiene | |
| includePermissions | No | Incluir permisos del usuario |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description presents the tool as purely returning information, but the parameter createDefaultScope implies it may create a default scope as a side effect. This potential mutation is not disclosed in the main description, and there are no annotations to clarify behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that directly communicates the core behavior without unnecessary detail or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description tells the caller what will be returned and the parameter descriptions explain the flags, but it does not mention the possible side effect of createDefaultScope or provide any output structure. Since there is no output schema, a bit more context about the response shape or side effects would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both parameters are covered by the schema with clear descriptions, so schema coverage is 100%. The main description does not add much detail about how the parameters affect the result, but the schema descriptions are sufficient for basic understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the authenticated user's profile, their scopes, and optionally their permissions. The verb 'Devuelve' and resource 'perfil del usuario autenticado' make the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus related tools such as get_my_permissions, get_my_scopes, or update_my_profile. The description only states what it does, not when it should be preferred over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.