get_equipment_detailsDetalhes completos de um equipamento: especificações, prós e contras, preço ao vivo. Use depois de search_equipment quando o usuário quiser saber mais sobre um produto específico.
| Name | Required | Description | Default |
|---|---|---|---|
| productPath | Yes | O productPath exato retornado por search_equipment. |
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 establish that the tool is read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond the annotations by specifying what content is returned and that the price is 'ao vivo' (live), while also indicating a dependency on the productPath from search_equipment.
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 two sentences with no wasted words. It front-loads the output content and immediately follows with the usage context and dependency, making it easy for an agent to parse quickly.
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 simple read-only lookup with one required parameter, the description is complete enough: it names the input, the output categories, and the exact usage sequence. The annotations cover the safety profile and no output schema is needed given the straightforward content list.
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?
Schema description coverage is 100%, and the schema already documents that productPath must be the exact value returned by search_equipment. The tool description reinforces this dependency but does not add meaningful new parameter-level semantics beyond what the schema provides.
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 what the tool returns: complete equipment details including specifications, pros and cons, and live price. It also distinguishes this tool from search_equipment by framing it as the follow-up step for a specific product.
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 explicitly says to use it after search_equipment when the user wants more information about a specific product. This gives the agent a clear, actionable trigger condition for invoking this tool versus the sibling search tool.
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 clear resource-action pair: search_* finds entities, get_* retrieves details, and build_tralha composes a full kit. The explicit cross-reference in get_lures_for_species and build_tralha prevents overlap with search_equipment.
All tool names follow a consistent verb_noun snake_case pattern: search_ for queries, get_ for details, and build_ for the one assembly action. The Portuguese term 'tralha' is domain-specific but does not break the pattern.
12 tools is well within the ideal 3-15 range and each one earns its place across species, equipment, locations, techniques, conditions, and kit assembly. The count feels intentionally scoped for a fishing assistant without bloat.
The surface covers the full discovery-to-recommendation journey: search species/equipment/locations/techniques, get detailed information, check fishing conditions, and assemble a complete rig. Domain-specific needs like lure-to-species mapping and river routes are also covered, leaving no obvious dead ends.