Skip to main content
Glama

CryptoExchange.Discount Referral Codes

Get Referral Link

getReferralCode
Read-onlyIdempotent

Get the current referral code, offer details, and signup URL for a specific exchange or product.

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": {
      "exchange": "<exchange>"
    },
    "name": "getReferralCode"
  }
}

Input Schema

NameRequiredDescriptionDefault
exchangeYesExchange or product name, slug, or code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 safety and side-effect behavior are covered by structured data. The description adds genuine value beyond that by enumerating what the caller receives (referral code, offer details, signup URL), which matters because there is no output schema. It does not mention auth requirements or what happens when an exchange has no active referral offer, keeping it below 5.

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?

One sentence, front-loaded with the verb and the returned payload, with the scoping condition at the end. No filler or redundancy; every clause identifies either the output or the target.

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 one-parameter, read-only lookup with rich annotations and no output schema, the description covers purpose and return contents adequately. The only remaining gap is the absence of a fallback or error expectation when no referral code exists for the given exchange, which is minor for this complexity level.

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% and the single parameter is already documented as accepting an exchange or product name, slug, or code. The description's wording of "exchange or product" mirrors the schema rather than adding new meaning such as matching rules or case sensitivity. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description gives a specific verb ("Get") and names the exact resource bundle returned: referral code, offer details, and signup URL, scoped to one exchange or product. That is clearly distinguishable from listDiscounts and searchExchanges, which are collection-oriented. It stops short of 5 only because it never explicitly contrasts itself with those siblings.

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?

The phrase "for a specific exchange or product" implicitly tells the agent this is a lookup for an already-known entity, not a discovery call, which nudges toward searchExchanges when the exchange is unknown. However, there is no explicit when-to-use statement, no exclusions, and no named alternative, so the routing is inferred rather than stated.

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