Skip to main content
Glama

Arc catalogue search

arc_catalogue_search

Who sells this on Arc, and for how much? Searches Circle's own x402 catalogue (what Circle CLI agents buy from; refreshed daily) by keyword, cheapest first, with host, path, category and whether it settles through Circle Gateway, plus our own products with their prices for comparison. Use it to price a service before you build or buy it. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arc_catalogue_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoup to 40 (default 15)
queryNokeywords, e.g. "scrape", "token price", "email"
networkNoarc (default), base, polygon, solana or any
maxPriceNooptional price cap in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that results are sorted cheapest-first, that the catalogue is refreshed daily, that it includes Circle's own products alongside the market, the exact fields returned (host, path, category, Gateway settlement), and that the call is free. It stops short of disclosing pagination behavior beyond the schema's limit, or any rate limits.

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

Conciseness4/5

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

The lead question front-loads the user intent, followed by a dense sentence covering source, sort order and returned fields. The parenthetical 'what Circle CLI agents buy from' is informative but adds a slight clutter; overall it is tight with no filler.

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?

For a four-optional-parameter read-only search with no output schema and no annotations, the description covers what it returns, freshness, ordering, cost and use case. Only result pagination details and output formatting are left implicit, which is a minor gap.

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 coverage is 100%, so the schema already documents query, network, maxPrice and limit with examples. The description reinforces keyword searching and cheap-first ordering, but adds no syntax or edge-case guidance (e.g. how network interacts with the Arc catalogue, or how maxPrice combines with the default sort) beyond what the schema supplies. Baseline 3 is appropriate.

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: 'Searches Circle's own x402 catalogue ... by keyword, cheapest first', and names the distinguishing data source (Circle CLI agent purchases, refreshed daily) plus the returned fields. It does not name any sibling such as market_search or arc_agent_search, so the agent must infer how it differs from those similarly named tools, which keeps it short of a 5.

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?

'Use it to price a service before you build or buy it' gives a clear triggering scenario, and the opening question frames the user intent it answers. There are no exclusions or explicit pointers to alternatives, which is the only thing separating it from a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources