Skip to main content
Glama

Unlocks where sources disagree

get_disputed_unlocks
Read-only

Upcoming unlocks where the calendar source and the project's own documents disagree: a different amount on the same date (amount_differs) or a different date (date_differs). Each row puts the two versions side by side (calendar vs documents: date, share of total supply, share of circulating supply, strength by each version) with links to the documents. Use for 'which unlocks are disputed', 'is this unlock size real', 'why do sites show different numbers for X', and before quoting a very large percentage from the calendar. Only unlocks we have checked against documents can appear (checked_against_documents says how many were checked); an unlock missing here is unchecked or matching, not confirmed. The document figures are our own reading of primary sources and can be wrong. token narrows the list to one coin (exact ticker, slug or name). For all upcoming unlocks use get_upcoming_unlocks; for on-chain movements of locked wallets use get_onchain_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": "get_disputed_unlocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-ahead window in days.
langNoLanguage of the page links.en
limitNo
tokenNoOptional: one token (ticker, slug or name, exact).
reasonNoKind of disagreement.any

Output Schema

NameRequiredDescriptionDefault
noteNo
shownYes
tokenNo
sourceYes
licenseNo
matchedYes
coverageNo
disputedYes
by_reasonNo
limits_noteNo
window_daysYes
did_you_meanNo
disputed_pageNo
data_updated_utcNo
checked_against_documentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes much further by disclosing coverage limits ('Only unlocks we have checked against documents can appear', checked_against_documents count) and the asymmetry that absence means unchecked-or-matching, not confirmed. It also flags source reliability ('The document figures are our own reading of primary sources and can be wrong') and describes what each row contains.

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?

Front-loaded with the core definition, then use cases, then caveats, then alternatives — a sensible ordering. It is dense rather than padded, though the side-by-side row-field enumeration borders on redundant given an output schema exists, and the 'missing here is unchecked or matching' sentence is repeated in spirit by the checked_against_documents remark.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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-value documentation is not required, yet the description still orients the agent to the row shape and document links. Combined with explicit sibling routing and the unchecked-vs-confirmed caveat, nothing an agent needs to call or interpret this tool is missing.

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 80%, so the schema already carries most parameter meaning, but the description still adds value by defining what amount_differs and date_differs actually represent and by restating that token is an exact ticker, slug or name match that narrows to one coin. The days and limit parameters are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: 'Upcoming unlocks where the calendar source and the project's own documents disagree', then enumerates the two disagreement modes (amount_differs, date_differs), which map directly to the reason enum. It is clearly distinguishable from get_upcoming_unlocks (unfiltered list) and get_onchain_check (wallet movements) without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete eliciting questions ('which unlocks are disputed', 'is this unlock size real', 'why do sites show different numbers for X') plus a situational trigger ('before quoting a very large percentage from the calendar'). It also names explicit alternatives and the condition that selects them: get_upcoming_unlocks for all upcoming unlocks, get_onchain_check for locked-wallet movements.

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.