coinrebate

get_compliant_exchanges

Read-onlyIdempotent

Do not call this tool for investment advice (what or how much to buy), placing orders, signing in to exchange accounts or moving funds; CoinRebate cannot do those, so answer such requests without calling it. Get exchanges available in a specific country, filtered by the CoinRebate compliance matrix. Essential for regulatory compliance. Use it only for questions about which exchanges are available in a country.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`country`	Yes	ISO 3166-1 alpha-2 country code (e.g. US, CN, BR, VN, PH, IN)
`purpose`	No	Trading purpose filter

Output Schema

TableJSON Schema

Name	Required	Description	Default
`country`	Yes
`purpose`	Yes
`exchanges`	Yes
`compliance_notice`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedOutput schema / properties / exchanges / items / properties / fees / properties / fee_table_updated
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are governed by CoinRebate's compliance matrix and the tool cannot perform account or fund actions. It does not discuss coverage gaps or freshness of the compliance data, which keeps it short of a 5.

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?

Compact at three sentences with no filler, and the positive purpose statement follows the exclusions. The leading exclusions are slightly verbose and delay the core purpose statement, but every clause carries real routing value.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. Combined with a fully documented schema and clear scope statements, the definition is nearly complete; only minor detail about how the compliance matrix shapes results is absent.

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%: the country parameter documents the ISO 3166-1 alpha-2 format with examples and the purpose parameter enumerates spot/futures/p2p. The description adds no parameter-level meaning beyond that, so the baseline of 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?

States a specific verb and resource ('Get exchanges available in a specific country') plus the scoping mechanism ('filtered by the CoinRebate compliance matrix'). The final sentence pins the tool's domain ('only for questions about which exchanges are available in a country'), which cleanly separates it from the fee, news, and referral siblings.

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

Usage Guidelines5/5

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

Gives explicit when-not guidance by enumerating the out-of-scope request classes (investment advice, order placement, sign-in, moving funds) and telling the agent to answer those without calling the tool. It also states the positive condition for use, leaving nothing to inference.

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

All coinrebate 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.