angel_get_methodologyExplica cómo Ángel analiza campañas, datos, web y procesos, incluyendo límites y criterios de priorización.
| 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 mark the tool as read-only and idempotent, so the description does not need to restate safety. It adds useful behavioral context by specifying what the methodology covers and that it includes limits and prioritization criteria. No contradiction with annotations exists.
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, well-structured sentence that front-loads the main purpose and then lists the concrete content areas. Every phrase adds meaningful information with no redundancy.
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?
Given zero parameters, a safe read-only annotation set, and an existing output schema, the description provides sufficient context. It clearly enumerates what content the tool covers, making it complete for an agent to decide when to invoke it.
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 input schema is empty, so there are no parameters to clarify. A baseline of 4 applies because no parameter documentation is needed.
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 explains Ángel's methodology for analyzing campaigns, data, web, and processes, including limits and prioritization criteria. This is specific and distinguishes it from sibling tools like get_contact, get_profile, and get_service, which target different resources.
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 implies when to use it: whenever someone needs an explanation of Ángel's working method, analysis criteria, or priorities. However, it does not explicitly mention alternatives or state when not to use this tool, leaving some routing to inference.
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.