Skip to main content
Glama

Explore21 MCP

Explain a metric

explain_metric
Read-only

What a metric measures, its columns and units, its method version and every change to how it is computed, and its chart page. 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": "explain_metric"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe metric id, e.g. bitcoin-realized-price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral detail beyond them: the response is reference material (method version, changelog, chart page) and includes a closing 'Source:' line that must be surfaced to the user — a non-obvious output obligation.

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?

Three short sentences, front-loaded with the returned content, then scope, then the output instruction. The opening sentence is a long verbless noun phrase, but no sentence is padding.

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 burden of describing returns and does so thoroughly (measures, units, columns, version, changelog, chart page, Source line). Only minor gaps remain, such as response size or behavior on an invalid id, which the enum largely prevents.

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?

There is a single required parameter whose schema description coverage is 100% and whose enum already constrains the ids, so the schema does the heavy lifting. The description adds no meaning about id selection or format, which matches the baseline of 3 for high schema coverage.

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 description enumerates exactly what the tool returns for a metric: what it measures, columns and units, method version, full change history, and the chart page. That is more specific than a restatement of the name, and it implicitly separates it from value-fetching siblings like get_metric, though no sibling is named explicitly.

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 context is implied rather than stated: 'Long-term context for Bitcoin holders, not trading signals' rules out a trading-signal use case but never says when to call this instead of get_metric or list_metrics. An agent must infer that this is the documentation/definition lookup and the others are data lookups.

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