Juegos que ahora mismo estan en su minimo historico o por debajo de su precio habitual. Usalo cuando pregunten que ofertas hay hoy.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | all_time_low, below_usual o all | |
| limit | No | Maximo 50 | |
| platform | No | pc, ps5, ps4, xbox-one, switch |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden of behavioral disclosure. It does state what the tool returns, but it omits key behavioral details such as the default behavior when no parameters are supplied, whether the result is a list, and how the 'type' filter combines with 'platform' and 'limit'. This leaves gaps for a read-only query tool.
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 redundancy. The first sentence front-loads the core behavior, and the second provides a direct usage trigger. Every phrase earns its place.
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 the tool's simplicity, full parameter schema, and absence of an output schema, the description reasonably covers the core action and trigger. It does not describe default parameter behavior or explicitly route to sibling tools, but these are minor gaps for a straightforward deal-listing tool.
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%, with all three parameters having descriptions in the schema. The description itself adds no parameter-specific meaning, such as the effect of leaving parameters empty or how type interacts with platform. This meets the baseline of 3 but does not exceed it.
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 identifies the resource (games) and the specific criterion (historical minimum or below usual price), which precisely defines what the tool returns. The phrase 'ofertas hay hoy' distinguishes it from siblings like get_price_history or get_upcoming by focusing on current deals.
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 states when to use the tool: 'Usalo cuando pregunten que ofertas hay hoy.' This is a clear context for the agent. However, it does not mention alternatives or when not to use it, so it stops short of a full 5.
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 addresses a distinct user need: current best price for a specific game, available deals, historical price trends, upcoming releases, and game search/resolution. There is minimal overlap, and the descriptions make it clear when to use each one.
All tool names follow the same verb_noun snake_case pattern: get_best_price, get_deals, get_price_history, get_upcoming, and search_game. The consistent structure makes the tool set predictable and easy for an agent to navigate.
With five tools, the server is well-scoped for game pricing and deals. Each tool covers a distinct aspect of the domain without redundancy or unnecessary bloat.
The tool surface covers the full game price workflow: search for a game, check current best price, see active deals, view historical prices, and look up upcoming releases. No significant gaps are apparent for a price-comparison focused server.
