Skip to main content
Glama

CryptoExchange.Discount Referral Codes

Search Exchange Offers

searchExchanges
Read-onlyIdempotent

Search crypto exchanges, wallets, analytics tools, and crypto cards by name, promo code, or feature.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "searchExchanges"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matches to return.
queryYesExchange, wallet, tool, feature, or promo code to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing behavioral beyond them: it does not say whether matching is exact or fuzzy, how results are ranked, whether promo-code lookups return offers, or how the limit truncates results.

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?

A single front-loaded sentence with no filler or redundancy. The core action and searchable fields appear first, and nothing is wasted.

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

Completeness3/5

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

For a simple read-only search with rich annotations and a fully documented schema, the definition is minimally adequate. It omits match semantics and result-ordering behavior, which matter for an agent deciding whether a query will find what it needs, and there is no output schema to fill that 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%, with both query and limit documented in the schema itself, so the baseline is 3. The phrase 'by name, promo code, or feature' loosely restates what the query parameter description already says, adding no new syntax or format guidance.

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?

A specific verb (search) plus an enumerated set of resources (exchanges, wallets, analytics tools, crypto cards) and match keys (name, promo code, feature). It clearly reads as a lookup tool, but it never contrasts itself with the sibling tools getReferralCode and listDiscounts, so the differentiator is inferred 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 Guidelines3/5

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

Usage is implied by 'search ... by name, promo code, or feature', giving an agent a sense of when a keyword lookup applies. There are no explicit when-to-use or when-not-to-use rules, and no pointer to the sibling tools for cases like listing codes or discounts.

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