Amazap

Search catalog

search_catalog

Read-onlyIdempotent

Find paid Amazap tasks by keyword. Results: price, value (est. saving), buy call.

Input Schema

Name	Required	Description
`limit`	No	How many SKUs to return. Default 8, maximum 20. (minimum 1).
`query`	Yes	Keywords or a short description of what you want to buy.
`cursor`	No	Page cursor from the previous search. When set, it overrides offset.
`offset`	No	How many matching SKUs to skip. Use nextCursor from the previous page when it is present. (minimum 0).
`region`	No	ISO country code. Matches coverage that includes it or is global. Unknown coverage stays in the results, ranked lower.
`protocol`	No	Optional filter: L402, x402 for Lightning x402, or usdc.
`buyable_only`	No	Hide SKUs that are not buyable yet, including USDC coming-soon rows. Default true. Pass false to see them. Buyable rows still rank first.
`include_demo`	No	Include synthetic demo SKUs. Default false.
`usd_per_million`	No	Your model input price in dollars per million tokens. Pass it once. This session reuses it. It does not change the Amazap price.
`include_unhealthy`	No	Include paused SKUs and untested SKUs with a generic schema. Default false.

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

addedInput schema / properties / usd_per_million

Added value: +{
+  "description": "Your model input price in dollars per million tokens. Pass it once. This session reuses it. It does not change the Amazap price.",
+  "type": "number"
+}

First observedOct 20, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds that results include price, estimated saving value, and a buy call, but does not expand on ranking, pagination behavior, or result limits.

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?

Two short sentences with the core action front-loaded and no wasted text. The result summary is terse but efficient.

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

Completeness4/5

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

The description covers the core search purpose and hints at returned fields, while the detailed schema and output schema carry the rest. It is complete enough for invocation, though a complex ten-parameter search with many siblings could benefit from a bit more routing context.

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

Parameters3/5

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

Schema description coverage is 100%, so all ten parameters are already documented in the schema. The description adds no parameter-specific meaning beyond the keyword-focused purpose and result summary, which is acceptable given the high schema coverage.

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 and resource: finding paid Amazap tasks by keyword. The purpose is clear, but it does not distinguish itself from siblings such as describe_sku, catalog_stats, or buy_best.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this search versus alternatives like describe_sku, quote, buy, or buy_best. The usage is only inferable from the tool name and purpose.

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?