Coinbase Exchange

Coinbase Exchange Product

coinbase_exchange_product

Read-onlyIdempotent

Single product.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "BTC-USD"
    },
    "name": "coinbase_exchange_product"
  }
}

Input Schema

Name	Required	Description	Default
`product_id`	Yes

Output Schema

Name	Required	Description
`id`	No	Product ID
`status`	No	Product status
`post_only`	No	Post-only orders
`limit_only`	No	Limit orders only
`cancel_only`	No	Cancel only
`display_name`	No	Display name
`base_currency`	No	Base currency
`base_max_size`	No	Maximum order size
`base_min_size`	No	Minimum order size
`margin_enabled`	No	Margin trading enabled
`quote_currency`	No	Quote currency
`quote_increment`	No	Quote increment

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured fields. The description adds nothing beyond that — no note on lookup failure behavior for an unknown product_id, no caching or live-data caveats, despite openWorldHint implying live exchange data.

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

Conciseness2/5

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

Two words are not conciseness here but under-specification; the text is trivially front-loaded because there is nothing to front-load. No sentence earns a place because no informative sentence exists.

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

Completeness2/5

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

Because an output schema exists, return values need not be explained, which lowers the bar. Still, an agent gets no definition of what a 'product' contains or what product_id format is accepted, which is inadequate even for a simple one-parameter lookup.

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

Parameters2/5

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

Parameter count is one with 0% description coverage; the only hints about the required product_id come from the schema's inline examples ("BTC-USD", "ETH-USD"-style pairs). The description does not state that the parameter is a hyphenated base-quote pair or what the valid universe is, so it fails to compensate for the coverage gap.

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

Purpose2/5

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

"Single product." restates the resource noun from the name/title without a verb, so the agent must infer that this retrieves one product record rather than listing them. The word "Single" weakly distinguishes it from the plural sibling coinbase_exchange_products, but that differentiation is implicit rather than stated.

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 when-to-use guidance, no mention of the list-style alternative, and no stated precondition such as needing a valid exchange product id. The only hint at routing is the adjective "Single", which an agent must decode on its own.

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

All Coinbase Exchange 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.