Devuelve la ficha de una calculadora por slug: qué inputs toma (id, tipo, requerido, valores válidos) y una URL de ejemplo. Usalo antes de compute para saber qué parámetros pasar.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | slug de la calc (ej. calculadora-imc) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It describes return content but does not mention idempotency, failure modes, or permissions. Adequate but not thorough.
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?
Two sentences in Spanish, front-loaded with purpose and usage advice. No redundant information.
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 low complexity (1 required param, no output schema), the description covers purpose, usage, and return content sufficiently. Could mention error handling or output structure, but not necessary for this simple retrieval.
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 coverage is 100% with a clear description for 'slug'. The tool description adds little beyond restating the parameter's role, earning a baseline score.
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 it returns calculator details by slug, including inputs and example URL. It distinguishes itself from siblings 'compute' and 'search_calculators' by advising use before compute.
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?
Explicitly advises to use before compute to know parameters, providing clear context. Could be stronger with explicit when-not-to-use, but the sibling names imply alternatives.
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 has a unique and clear purpose: search finds calculators, get_calculator retrieves details, and compute performs calculations. No overlap exists.
All tools use lowercase with underscores and follow a verb_noun pattern (search_calculators, get_calculator, compute). Consistent naming convention.
Three tools is ideal for this domain: discover, inspect, and compute. Each tool earns its place without unnecessary bloat.
The tool surface covers the full workflow: searching for calculators, retrieving their input schema, and computing results. No obvious gaps.