Amazap

Quote

quote

Read-onlyIdempotent

Free price check incl. value estimate (raw vs output tokens, break-even $/M). Call only to change quantity/currency or check value before buying. When Lightning payments are temporarily paused, the result includes paymentsPaused and retryAfter.

Input Schema

Name	Required	Description
`sku`	No	Catalog id or slug from search_catalog. Omit when items is set.
`items`	No	Basket to price. One entry per SKU. A repeated line is refused unless confirm_duplicates is true on this call or on that line. Does not spend sats. Copy buy.quote_id into buy.
`params`	No	Optional fields to check before payment. An object, or a JSON array when the SKU body is an array. An invalid value, including a page URL that is not http or https, is rejected. The quote does not spend sats.
`baseline`	No	Accepted for older clients. Savings use the page's visible text. raw is ignored.
`currency`	No	ISO 4217. Default USD. Includes MXN.
`quantity`	No	How many calls to price. Default 1, maximum 3.
`accept_terms`	No	Optional. When this covers the current terms, the account stores that acceptance. The quote still does not spend sats.
`usd_per_million`	No	Your model input price in dollars per million tokens. Default 2. This does not change the Amazap price.
`confirm_duplicates`	No	Set true only to price the same line more than once. Otherwise a repeated line is refused and nothing is charged.

Output Schema

Name	Required	Description
`code`	No	approval_required, limit_exceeded, or insufficient_balance.
`paid`	No
`which`	No	per_call, per_day, per_session, per_hour_buys, per_minute_calls, or per_minute_sats.
`status`	No
`message`	No
`quoteId`	No
`results`	No	Search rows when this is a search result.
`totalCost`	No
`totalSats`	No
`approvalUrl`	No	Page where the person approves this exact price.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / usd_per_million / description

Previous value: -"Your model input price in dollars per million tokens. Default 1.25. This does not change the Amazap price."New value: +"Your model input price in dollars per million tokens. Default 2. This does not change the Amazap price."

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / accept_terms

Added value: +{
+  "description": "Optional. When this covers the current terms, the account stores that acceptance. The quote still does not spend sats.",
+  "type": "string"
+}

First observedOct 20, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: the paused-Lightning case returns paymentsPaused and retryAfter, which an agent could not infer from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core purpose, then usage constraint, then the edge-case behavior. No filler and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers the one non-obvious response case (paymentsPaused/retryAfter). Single-SKU vs basket branching is fully handled by the schema's oneOf, leaving no critical gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds interpretive value by tying quantity/currency to the re-quote trigger and framing usd_per_million as a break-even computation rather than just a model input price.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource — a free price check that returns a value estimate (raw vs output tokens, break-even $/M). This clearly separates it from mutating siblings like buy, though the sibling is only implied via 'before buying', not named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call only to change quantity/currency or check value before buying' gives explicit when-to-use context and implicitly scopes out other cases. It stops short of naming the alternative tool (buy) or spelling out when a quote is unnecessary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Amazap tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?