Skip to main content
Glama

How unlocks are rated, and what happened before past ones

get_method_and_track_record
Read-only

Explains the strong / medium / small rating and gives the historical record: for past unlocks of each strength, how often the token fell against Bitcoin in the week before the unlock and the average move. Use when the user asks what 'strong' means, whether unlocks move prices, or how reliable the rating is. Not a forecast for any single token.

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_method_and_track_record"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourceYes
licenseNo
measureNo
readingNo
thresholdsYes
method_pageNo
track_recordYes
data_updated_utcNo
live_journal_pageNo
track_record_windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data_updated_utc": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "license": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "live_journal_page": {
      +      "type": "string"
      +    },
      +    "measure": {
      +      "type": "string"
      +    },
      +    "method_page": {
      +      "type": "string"
      +    },
      +    "reading": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "thresholds": {
      +      "type": "object"
      +    },
      +    "track_record": {
      +      "type": "object"
      +    },
      +    "track_record_window": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "source",
      +    "thresholds",
      +    "track_record"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and an output schema exists, so the bar is lower. The description still adds meaningful context by stating the shape of the evidence (per-strength frequency and average move in the pre-unlock week) and by explicitly warning that the output is aggregate, not a single-token prediction.

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

Conciseness5/5

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

Three sentences, each earning its place: what it returns, when to call it, and what it is not. The purpose and scope are front-loaded before the usage triggers.

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?

A zero-parameter, read-only explanation tool with an output schema and annotations covering safety and openness. The description supplies exactly the missing piece — the semantics of the rating and the aggregate nature of the results — with nothing an agent needs left unstated.

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?

The tool takes no parameters and the schema is an empty object with additionalProperties false, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly does not waste words on inputs.

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 pair ('Explains the strong / medium / small rating and gives the historical record') plus the exact contents of that record (hit rate against Bitcoin in the week before, average move). The closing line 'Not a forecast for any single token' separates it from the data-fetching siblings like get_upcoming_unlocks, so an agent can route without opening schemas.

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

Usage Guidelines4/5

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

Gives explicit trigger phrases: user asks what 'strong' means, whether unlocks move prices, or how reliable the rating is. It also sets a scope boundary ('Not a forecast for any single token'), though it does not name a sibling to use instead for per-token forecasting, leaving that inference to the agent.

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.