Skip to main content
Glama

CryptoExchange.Discount Referral Codes

List Verified Discounts

listDiscounts
Read-onlyIdempotent

List the highest-rated verified discounts currently featured on the site.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of offers to return.
categoryNoOptional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral detail beyond that: results are curated by rating ("highest-rated") and limited to "currently featured" items, which tells the agent the ordering and freshness of the output. It does not describe the returned fields or whether promotion/expiry affects results.

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?

A single well-formed sentence with the ranking qualifier front-loaded and no wasted wording. It is perhaps slightly too terse for a tool with two filters, but there is 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 low-complexity, non-destructive, closed-world list tool with two optional parameters and a fully documented schema, the definition covers what an agent needs to call it. The lack of any hint about returned fields is a minor gap given there is no output schema.

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%, with both `limit` (default 12, max 25) and `category` (enum) fully documented in the schema, so baseline is 3. The description adds no further meaning about how `limit` interacts with ranking or how `category` narrows the featured set.

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 ("List") and resource ("verified discounts") plus a scope qualifier: highest-rated and currently featured. It is distinguishable from the sibling tools (referral codes, exchange search) by subject matter, though it does not name or contrast any alternative explicitly.

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?

No when-to-use or when-not-to-use guidance is given; the sentence only asserts what the result set contains. An agent must infer that this is the browse/discovery tool for featured verified discounts rather than being told so, and there is no mention of how it relates to searchExchanges.

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