Tipos de cambio de REFERENCIA del día en Perú: el oficial SBS/SUNAT, el dólar paralelo/informal y el USDT P2P (cripto). NO son casas de cambio — sirven para contextualizar y comparar contra el ranking de mejor_tasa.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the three specific rate types, clarifies that these are not exchange houses, and explains the intended purpose (contextualization). This adequately sets expectations for a read-only data tool, though it omits details like update frequency or output format.
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 concise sentences. It front-loads the core purpose, enumerates rate types, clarifies a boundary, and states usage context. Every clause carries 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?
For a zero-parameter tool with no output schema, the description covers the essential aspects: what it provides (three reference rates of the day), what it is not (exchange houses), and how to use it (compared against mejor_tasa). It could specify the output structure, but the simplicity of the tool makes the description reasonably complete.
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 per the rubric the baseline is 4. The description compensates by explaining the content of the result (rate types) and their purpose, adding value beyond the empty schema.
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 reference exchange rates for the day in Peru, explicitly listing the types (official SBS/SUNAT, parallel/informal, USDT P2P). It also distinguishes itself from sibling tool mejor_tasa by clarifying it provides contextual data, not actual exchange house rates.
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 provides usage context: the rates 'sirven para contextualizar y comparar contra el ranking de mejor_tasa' – they are for context/comparison, not for actual exchange. It also explicitly negates 'NO son casas de cambio', which tells the agent when not to use it and implies mejor_tasa as the alternative for actual rates.
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 clearly distinct purpose: one provides live rankings of exchange houses, the other provides reference rates for context. There is no overlap in functionality, making it easy for an agent to select the right tool.
Both tool names are descriptive Spanish noun phrases with underscores, though they don't follow a strict verb_noun pattern. The naming is clear and readable, with only minor stylistic deviation between them.
With only 2 tools, the server feels thin but is appropriate for the narrow domain of Peruvian exchange rates. It is a borderline case, as more tools could be added for historical data or detailed exchange house information.
The tool set covers the core need: finding the best exchange rate and contextualizing it with reference rates. Minor gaps like historical trends or detailed house profiles exist but are not essential for the primary use case.