get_pricing_ratesEasy's flat-rate pricing per payment channel (cards, ACH, wallets, stablecoins) as structured JSON — the same numbers published on /pricing. No monthly or setup fees.
| Name | Required | Description | Default |
|---|---|---|---|
| channel | No | Optional single channel; omit for all rates |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so this is known to be a safe read operation. The description adds useful context by stating this returns the same published numbers as /pricing and mentions 'No monthly or setup fees,' but it does not cover auth/rate limits or return-value details. That is acceptable for a simple public pricing endpoint.
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 short, front-loaded with the core resource and purpose, and every sentence adds information. The parenthetical channel list and the no-fees note are useful without bloating the text.
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?
With one optional parameter, no output schema, and a read-only annotation, the description covers the important context: what pricing is returned, in what format, and where the numbers come from. It stops short of detailing the exact JSON shape, but the low complexity and schema documentation make the tool adequately specified.
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 schema already fully documents the single 'channel' parameter with 100% coverage, so the baseline is 3. However, the description lists 'wallets' as a payment channel, while the schema enum contains only card-domestic, card-amex, card-international, card-keyed, ach, and stablecoin. This mismatch could lead an agent to pass an invalid value like 'wallets'.
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 names the resource ('Easy's published processing rates' / 'flat-rate pricing per payment channel') and specifies the output form ('structured JSON'). It also enumerates the pricing categories, making it easy to distinguish from the page-focused sibling tools.
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 gives clear context: use this tool to retrieve Easy's published flat-rate pricing as JSON, with the same figures as /pricing. It does not explicitly name alternatives or exclusions, but the purpose is sufficiently distinct from get_page and list_pages that no alternate routing is needed.
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.
get_page and get_pricing_rates both touch pricing content, but one returns rendered page markdown and the other returns structured JSON, so their purposes are mostly clear. list_pages is distinctly the discovery tool for page paths.
All tool names follow a consistent verb_noun snake_case pattern: get_page, get_pricing_rates, list_pages. The verbs 'get' and 'list' are used predictably for their respective actions.
Three tools is well-scoped for a simple website content and pricing retrieval server. Each tool has a clear role: discover pages, read a page, and fetch structured pricing.
The server covers its apparent domain completely: list_pages provides the page index, get_page retrieves any page, and get_pricing_rates exposes structured pricing data. No major dead ends or missing operations for the stated scope.