Skip to main content
Glama

Explore21 MCP

List metrics

list_metrics
Read-only

Every Bitcoin metric Explore21 publishes, with its id and what it measures. Long-term context for Bitcoin holders, not trading signals. Show the closing "Source:" line to the user.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond them: it discloses completeness ('every metric published'), the shape of what comes back (id + what it measures), and an explicit output obligation to surface the closing 'Source:' line to the user — a display requirement that appears nowhere in the structured fields.

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 core purpose and the return contents. The audience framing is slightly promotional and the 'Source:' instruction is tacked on at the end rather than grouped with output expectations, but nothing is redundant or padded.

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 parameters, no output schema, and read-only annotations, the description covers what an agent needs: what the catalog contains, what each entry includes, and a required display behavior. It stops short of indicating list size or whether output may be long, which would matter for an 'every X' enumeration tool.

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 zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly makes no attempt to invent parameter guidance.

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?

States a specific verb+resource ('list every Bitcoin metric Explore21 publishes') and explicitly names the returned fields ('its id and what it measures'), which is more than a restatement of the name. It does not explicitly distinguish itself from siblings like get_metric or explain_metric, so the agent must infer that this is the full-catalog enumeration.

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?

The line 'Long-term context for Bitcoin holders, not trading signals' frames the intended audience and rules out one use case, which is useful implied guidance. However, it never says when to pick this over get_metric or explain_metric (e.g. 'call this first to discover ids, then pass them to get_metric'), so the routing decision is left to inference.

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