Skip to main content
Glama

Exchange.news — Crypto offers, campaigns and news

Search public offers

search_codes
Read-onlyIdempotent

Search brand aliases, categories and benefits. Generic promo/code words are ignored. Exact brand matches come first. Returns only catalog records; unknown queries return an empty array. Product and regional applicability remain subject to each caveat.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesSearch text, e.g. OKX EU stock perps discount.
offsetNo
regionNoOptional region context. Does not establish eligibility.
productNoOptional product context. Does not establish eligibility.

Output Schema

NameRequiredDescriptionDefault
countYes
totalYes
noticeYes
offsetYes
resultsYes
has_moreYes
disclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / results / items / properties / signup_note
      Added value: +{
      +  "type": "string"
      +}
  2. 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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: stop-word handling, exact-brand ranking, empty-array-on-miss, and that catalog hits do not confer product/regional eligibility. It does not discuss pagination behavior, but the output schema and annotations carry much of the rest.

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?

Five short sentences, front-loaded with what is searched, then ranking, then failure mode, then eligibility caveat — no filler. The closing phrase 'subject to each caveat' has an unclear referent, slightly blunting the otherwise tight structure.

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?

With five parameters, full annotations and an output schema, the description covers the essentials an agent needs: search scope, ranking, empty-result behavior, and eligibility limits. Minor gaps remain — pagination semantics are left entirely to the schema, and the vague 'each caveat' reference is not resolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60% and the schema already documents query, region and product with examples and eligibility caveats. The description still adds meaning: it explains how query text is normalized ('generic promo/code words are ignored') and reinforces that region/product are context only ('applicability remain subject to each caveat'). limit/offset are only covered by the schema, not the description.

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 uses a specific verb and clarifies the ambiguous resource name: it searches 'brand aliases, categories and benefits', which is more precise than the tool name search_codes or the title 'Search public offers'. It does not name any sibling (get_code, list_brands) or state what separates this search from them, so it stops short of a 5.

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 through query-behavior hints ('generic promo/code words are ignored', 'exact brand matches come first') and the note that unknown queries return an empty array, which tells the agent how to phrase and interpret searches. There is no explicit when-to-use/when-not guidance and no named alternative such as get_code for direct lookups, so the agent must infer the boundary.

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