Skip to main content
Glama

Exchange.news — Crypto offers, campaigns and news

List brands and public offers

list_brands
Read-onlyIdempotent

Browse brands with their public offer type, visible code or null, lifetime signup link and full conditions. Optional exact category filter. No live eligibility check.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
categoryNoOptional category: exchanges, wallets, cards, hardware, analytics or defi.

Output Schema

NameRequiredDescriptionDefault
countYes
totalYes
brandsYes
noticeYes
offsetYes
has_moreYes
disclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / brands / items / properties / signup_note
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds the meaningful caveat that eligibility is not validated live, implying potentially stale data. It also discloses that the code field may be null, which is real behavioral information rather than a restatement of the schema.

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?

Two compact sentences with the returned data front-loaded and the caveat trailing under it. 'Visible code or null' is slightly compressed phrasing but no sentence is wasted.

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 described, and the three parameters are simple pagination plus a filter. The description plus structured fields give enough to call the tool correctly; only the pagination bounds and the choice of alternative for eligibility are unaddressed.

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 33% and only the category parameter is documented there. The description compensates partially by clarifying that category filtering is exact, which the schema does not state, but limit and offset go unmentioned in both places and are left to their defaults.

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 and resource ('Browse brands') and enumerates what each entry carries: offer type, visible code or null, lifetime signup link, and full conditions. That is far more specific than the title, though it never explicitly contrasts itself with sibling list/search tools such as search_codes.

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?

'Optional exact category filter' gives a positive usage cue and 'No live eligibility check' functions as an explicit when-not (don't rely on this for eligibility verification). However, no alternative tool is named for that case, so the agent must infer where to go instead.

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