angel_get_profileDevuelve el perfil público, experiencia, especialidades y principios de trabajo de Ángel Moncada.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| metadata | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the useful context that the profile is 'público', suggesting no special authorization is needed, which is a modest behavioral insight beyond the annotations.
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?
A single, concise sentence fully captures the tool's purpose. It is front-loaded with the main object and lists the specific content areas without wasted words.
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?
For a zero-parameter, read-only profile retrieval tool with an output schema present, the description is complete. The annotations cover safety, and there are no missing inputs or behavioral details that an agent would need to call it correctly.
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?
The tool has zero parameters, so the description does not need to explain parameter semantics. The baseline of 4 applies because no compensation is necessary; the input schema is empty and fully self-explanatory.
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 uses a specific verb, 'Devuelve', and identifies a clear resource: Ángel Moncada's public profile, experience, specialties, and work principles. This distinguishes it from sibling tools like angel_get_contact or angel_get_methodology, which address different aspects.
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?
The description provides clear context for when to use the tool: whenever the agent needs Ángel Moncada's professional profile. It does not explicitly name alternatives or state exclusions, but the tool's scope is obvious from the content described.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of the public consulting domain: contact, methodology, profile, individual service details, case list, service recommendation, and cross-cutting search. The overlap between search and get_service is minimal because search returns matches with canonical URLs while get_service provides the full approved description of a specific service.
All tool names follow a consistent pattern: the prefix 'angel_' plus a clear verb ('get', 'list', 'recommend', 'search') followed by the target noun. This uniform verb_noun convention makes the tool set highly predictable and easy to navigate.
With 7 tools, the server is well-scoped for a consulting information and recommendation service. Each tool earns its place, covering both direct lookups (contact, profile, service, methodology) and discovery/guidance (list cases, recommend, search).
The domain of public consulting information is well covered: profile, methodology, services, cases, contact, and search are all present. A minor gap is the absence of a dedicated 'list_services' tool—an agent must rely on search or recommendation to discover available services—but this is not a fatal omission given the search capability.