Skip to main content
Glama

Explore21 MCP

Get a metric

get_metric
Read-only

One metric's daily values as CSV, oldest first. Without from/to it returns the last 365 days; pass from (and to) as yyyy-MM-dd for other ranges. Use list_metrics for the ids. Long-term context for Bitcoin holders, not trading signals. Show the closing "Source:" line to the user.

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": {
      "id": "<id>"
    },
    "name": "get_metric"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe metric id, e.g. bitcoin-mvrv-ratio.
toNoLast UTC day, yyyy-MM-dd.
fromNoFirst UTC day, yyyy-MM-dd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds the default 365-day window, CSV output ordering, and the unusual instruction to show the closing 'Source:' line to the user, which is genuinely beyond structured fields. It omits other behavioral details such as row-count limits or error behavior, so this lands at a solid 3 rather than higher.

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?

Four short sentences, front-loaded with what is returned and its ordering, followed by defaults, the sibling pointer, intent framing, and a required output step. Nothing is wasted or buried.

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 covers format (CSV), ordering (oldest first), default window, and the required Source citation line, which is enough for correct invocation. Only minor gaps remain, such as volume limits on a 365-day pull.

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 coverage is 100% and each parameter is already documented with pattern and format, so the baseline is 3. The description does add real meaning the schema lacks: the default range when from/to are omitted and the fact that from and to are used together.

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?

The description names the specific resource (one metric), the exact return shape (daily values as CSV, oldest first), and explicitly distinguishes itself from list_metrics, which supplies the ids. An agent can tell it apart from its siblings without opening the 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?

It states the default when from/to are omitted (last 365 days), how to request another range (pass from and to as yyyy-MM-dd), names the alternative for discovering ids (list_metrics), and scopes intent with 'Long-term context for Bitcoin holders, not trading signals.' Both when-to-use and when-not-to-use are covered.

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