Skip to main content
Glama

Check a list of coins for upcoming unlocks

check_portfolio
Read-only

Checks up to 50 tokens in one call and sorts them into three groups: with_unlocks (an unlock is scheduled within the window, nearest first), without_unlocks (we track the token and nothing is scheduled within the window) and unknown (the token is not in our data: this is NOT evidence that it has no unlocks). Use when the user gives a portfolio, a watchlist or several tickers ('I hold ARB, OP and SUI, any unlocks coming?'). Matching is exact on ticker, slug or name; an input that only partly matches goes to unknown with did_you_mean instead of a guess. Send tickers only: amounts and wallet addresses are not needed and not accepted. portfolio_page opens the same list on the website. For full details of one coin call get_token_unlocks; disputed=true on an unlock means the project's documents differ, report both versions.

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": {
      "tokens": "<tokens>"
    },
    "name": "check_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-ahead window in days.
langNoLanguage of the page links.en
tokensYesTickers (preferred), names or slugs, for example ["ARB","OP","sui"].
min_strengthNoLowest strength that counts as an unlock to report.small

Output Schema

NameRequiredDescriptionDefault
noteNo
sourceYes
licenseNo
summaryYes
unknownYes
requestedYes
limits_noteNo
window_daysYes
with_unlocksYes
portfolio_pageNo
without_unlocksYes
data_updated_utcNo
track_record_strongNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint it discloses genuinely non-obvious behavior: exact matching on ticker/slug/name, that partial matches fall to unknown with did_you_mean rather than a guess, and the critical caveat that unknown is 'NOT evidence that it has no unlocks'. It does not mention data freshness or latency, and the trailing note about disputed=true belongs to the single-coin tool, so it falls just short of a 5.

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 action and the three result groups, then the trigger, then the matching rules, so an agent gets the essentials in the first sentence. Slightly dense — the closing sentence about get_token_unlocks and disputed=true is arguably out of scope for this tool and could be trimmed.

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?

For a 4-parameter, read-only batch lookup with an output schema and full annotation coverage, nothing an agent needs is missing: trigger, identifier forms, cap, matching failure behavior, and the interpretation trap around unknown are all covered. Return structure is correctly left to the output schema.

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 100%, so the 3 baseline applies and the description exceeds it: it explains the accepted identifier forms for `tokens` (ticker preferred, then name, then slug), the 50-item cap, the exact-match failure path, and that the look-ahead window governs the with_unlocks grouping. It leaves min_strength and lang to the schema, which is reasonable since both are enumerated with defaults.

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 concrete verb and resource ('Checks up to 50 tokens in one call') and enumerates the exact output partition (with_unlocks, without_unlocks, unknown) with ordering semantics ('nearest first'). It is clearly distinguishable from get_token_unlocks (single coin, full details) and get_upcoming_unlocks, so an agent can choose without opening a 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 an explicit trigger with a realistic example ('I hold ARB, OP and SUI, any unlocks coming?'), names the alternative for the single-coin case ('For full details of one coin call get_token_unlocks'), and routes to portfolio_page for the web view. It also states a usage constraint: 'Send tickers only: amounts and wallet addresses are not needed and not accepted.'

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.