SiteCheck Crypto & Finance

Coinbase Exchange trading products with status and minimum

finance_coinbase_exchange_products

Read-only

Coinbase Exchange trading products (pairs) with status and minimum order sizes, filtered by quote currency (default USD). Lists what can be traded; no prices. Related tools on this server, for a different need: crypto_coinbase_spot_exchange when you need Coinbase Exchange order book for one product: best bid; finance_coinbase_orderbook_candles when you need Coinbase Exchange OHLCV candles for one product at 1m, 5m. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "finance_coinbase_exchange_products"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many products, 1 to 200 (default 20)
`quote`	No	Quote currency, e.g. USD, EUR, BTC (default USD)

Output Schema

Name	Required	Description	Default
`quote`	No
`source`	No
`products`	No
`checkedAt`	No
`totalForQuote`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-schema information: per-call cost ($0.002 USDC), payment rails (x402 on Base, Solana, Arc), and that failed calls are not charged — unusual and useful commercial context. It does not say whether results are paginated or how many products exist in total.

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

Conciseness3/5

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

The purpose is front-loaded in the first clause, which is good, but the rest collapses into a dense semicolon-and-colon run of sibling pointers and payment terms. Sentence fragments like "best bid" and "1m, 5m" read as truncated rather than compact, costing some clarity.

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?

With an output schema present, the description needn't explain return values, and annotations cover read-only/open-world. What an agent needs before calling — scope, defaults, cost, payment, and where to go for prices — is all present for a simple two-optional-parameter listing tool.

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%, with both parameters (limit 1–200 default 20, quote e.g. USD/EUR/BTC default USD) fully documented in the schema. The description restates the quote default and adds no syntax or behavior beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

The description states a specific verb and resource — listing Coinbase Exchange trading products (pairs) with status and minimum order sizes — plus the scope constraint (filtered by quote currency, default USD) and an explicit negative scope ("no prices"). That negative scope alone distinguishes it from the orderbook and candle siblings.

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?

It names two sibling tools and the need each serves (order book for one product, OHLCV candles for one product), which routes the agent away from this tool for price data. What's missing is a positive "use this when you need to discover tradable pairs/minimum sizes" framing; the guidance is delivered as exclusions rather than a when-to-use statement.

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

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?