Skip to main content
Glama

Token Command Center

tc_calendar

Read-only

Upcoming dated catalysts (unlocks, emission steps, votes, launches) across the Book, soonest first, at most 20. Optional token slug, tokens (several slugs), kind and horizon in days (default 30, max 180). Text is analyst notes; each event also has symbol, kind, estimated (date marked approximate), a plain title with title_source (curated: hand-written for this note; measured: from the measured unlock size; note: cut from the note), and the measured next unlock (pct_circ, pct_supply, tokens, source, as_of; CoinMarketCap) when it falls within a day of the event, else null. Events whose text starts 'Scheduled unlock' come from the measured schedule alone, fill only slots the analyst events leave free, and are counted in scheduled_total.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
kindNo
tokenNoToken slug to filter to.
tokensNoSeveral token slugs, e.g. the coins a person follows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / kind
      Added value: +{
      +  "enum": [
      +    "unlock",
      +    "emissions",
      +    "governance",
      +    "product",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / tokens
      Added value: +{
      +  "description": "Several token slugs, e.g. the coins a person follows.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes well beyond that by disclosing the 20-item cap, the default 30-day and max 180-day horizon, the estimated-date marker, the title_source taxonomy (curated/measured/note), the CoinMarketCap provenance and one-day matching rule for measured unlocks, and how 'Scheduled unlock' events backfill free slots and roll into scheduled_total. These are real behavioral traits an agent could not get from the annotations. Minor gap: pagination/truncation behavior when more than 20 events exist is not stated.

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?

The purpose and filters are front-loaded in the first two sentences, which is good. But the back half is a dense, semicolon-and-parenthesis-laden run of clauses about return fields and fallback mechanics that is hard to parse in one pass, and the capitalized term 'the Book' is used as unexplained jargon. Much of the detail is warranted given no output schema, but the packaging hurts readability.

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 no output schema, the description carries the return-value burden and largely does so: it enumerates event fields (symbol, kind, estimated, title, title_source, measured next unlock with pct_circ/pct_supply/tokens/source/as_of), the null condition, and the synthetic scheduled-event behavior. Remaining gaps are the meaning of 'the Book', the timezone/reference date for 'soonest first', and what happens beyond the 20-item cap.

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 only 50% — token and tokens are documented in the schema, but days and kind are not. The description rescues days (default 30, max 180, interpreted as a horizon in days) and implicitly maps kind to the catalyst categories in the parenthetical list, which adds some value. However it does not spell out the enum values or clarify how kind interacts with the 'Scheduled unlock' measured events, so the compensation is partial, landing this at the minimum-viable baseline rather than above it.

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 opening clause is a specific verb+resource statement: upcoming dated catalysts (unlocks, emission steps, votes, launches) with explicit ordering (soonest first) and a cap (at most 20). It is clearly a calendar/catalyst feed, distinguishable in substance from siblings like tc_series or tc_moves, though no sibling is named to make the boundary explicit.

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 only implied: an agent can infer this is the tool for forward-looking dated events, filtered by token/tokens/kind/horizon. There is no statement of when to prefer it over alternatives, no exclusion of past events, and no guidance on choosing token vs tokens or on choosing a horizon.

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