Skip to main content
Glama

ticker collision

ticker-collision
Read-onlyIdempotent

Same ticker = same token everywhere? Contract per chain on bitget, gate, htx, kucoin + price vs median on bitget, gate, htx, kucoin, mexc, okx -> CONSISTENT/DIVERGENT/COLLISION (anti-scam before deposit/arbitrage) Price: $0.05 per call, USDC on Base via x402.

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": {
      "coin": "<coin>"
    },
    "name": "ticker-collision"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesstring ticker, e.g. TRUMP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely non-schema behavior: a pay-per-call cost of $0.05 in USDC on Base via x402, which is important for an agent to know before invoking. Beyond that it says nothing about data freshness, latency, or what a partial-coverage result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the core question, but the middle clause ('Contract per chain on bitget, gate, htx, kucoin + price vs median on ...') is arrow-chained and telegraphic, requiring re-reading. The exchange lists are informative but could be stated more cleanly.

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?

With no output schema, the description must carry return-value meaning; it does so partly by naming the three verdict classes, but never explains what distinguishes DIVERGENT from COLLISION or whether per-chain contract addresses and median deviations are returned. For a single-parameter read tool with a payment requirement, that leaves a moderate 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 description coverage is 100% and the single 'coin' parameter is documented with an example (TRUMP), so the baseline is 3. The description's use of 'ticker' reinforces the parameter but adds no format, normalization, or case-handling detail beyond the schema.

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 states a specific check (same ticker = same token across chains?) and names the concrete artifacts it compares: per-chain contract addresses on bitget/gate/htx/kucoin and price vs median across six exchanges. It also states the output classes (CONSISTENT/DIVERGENT/COLLISION), which lets an agent identify the tool. It does not explicitly separate itself from siblings such as token-check, so it falls 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?

The parenthetical '(anti-scam before deposit/arbitrage)' supplies the use case, implying when to call it. There is no explicit when-not guidance, no prerequisite description, and no named alternative among the many token-check siblings, so usage is only implied.

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