Subscribe a webhook to fire when a provider changes prices (or read recent price changes). Pass webhook to subscribe (optionally filter by provider and direction 'cut'|'raise'); omit to read recent changes.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| webhook | No | HTTPS URL to POST price-change events to. Omit to just read recent changes. | |
| provider | No | ||
| direction | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It explains the two operational modes and filtering, but omits details like error handling, rate limits, or authentication requirements for webhook subscriptions.
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, concise sentence that efficiently conveys the tool's purpose and usage. No unnecessary words.
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?
The description is adequate for basic understanding but lacks details on return format for reading changes, error handling, and parameter constraints. No output schema exists to fill gaps.
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 description explains the webhook and direction parameters beyond the schema, but does not explain limit or provider. Schema coverage is low (25%), so the description only partially compensates.
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 that the tool subscribes a webhook to price changes or reads recent changes, using specific verbs and resources. It distinguishes itself from siblings like cheapest_model and price_history by focusing on alerts.
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?
It provides clear guidance on when to use each mode: pass webhook to subscribe, omit to read. It also mentions optional filters. However, it does not explicitly exclude alternatives or contrast with sibling tools.
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: cheapest model search, price change alerts, price history, and provider status. No overlap in purpose.
All tool names use lowercase with underscores and follow a predictable noun_noun or adjective_noun pattern. Naming is clear and consistent.
With 4 tools, the server is well-scoped for its purpose of monitoring AI API prices and status. Each tool is justified.
While core functionalities are covered, the server lacks a tool to list available providers or models, which is a notable gap for initial discovery.