Skip to main content
Glama

stats

Retrieve global AgentIndex statistics, including total agents, Bitcoin anchors, chain blocks, chat messages, and daily registrations.

Instructions

Get global AgentIndex statistics: total agents, Bitcoin anchors, chain blocks, chat messages, registrations today.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. Beyond the 'global' scope and the fact that it reports aggregates rather than per-user data, it says nothing about read-only semantics explicitly, authentication requirements, cost/rate limits, or freshness of the 'today' counters — all material for a metrics endpoint with zero annotation coverage.

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?

A single sentence, front-loaded with the action and scope, followed by the enumerated outputs. Every clause adds information and nothing is filler.

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?

For a simple zero-argument read with no output schema, the description appropriately compensates by naming the five values returned, which is what an agent needs to decide whether the call is worthwhile. The remaining gap is the total absence of behavioral framing (read-only, caching/freshness), which no other structured field covers.

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, so there is nothing for the description to disambiguate beyond what the schema already conveys; baseline for a zero-parameter tool is 4. The enumerated metric list usefully confirms that no filtering arguments are expected.

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 gives a specific verb and resource ('Get global AgentIndex statistics') and enumerates the exact metrics returned (total agents, Bitcoin anchors, chain blocks, chat messages, registrations today). This clearly separates it from every sibling, which are all action tools (mine, chat_send, register_agent, gate), none of which report aggregates.

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?

Use is only implied: an agent can infer this is for an overview/dashboard snapshot of the index, and the word 'global' signals it takes no scoping. The description never states when to prefer this over e.g. check_agent or balance for a specific figure, and gives no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.