Skip to main content
Glama
iota-mcp

iota-mcp

by qso-graph

Iota Stats

iota_stats
Read-onlyIdempotent

Retrieve IOTA programme summary statistics, including total groups and islands, continent breakdown, DXCC entity counts, and most or least credited groups for programme analysis.

Instructions

Get IOTA programme summary statistics.

Returns total groups and islands, breakdown by continent, DXCC entity count, and most/least credited groups.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and reproducibility are covered. The description adds value by disclosing the actual content of the payload (totals, continent breakdown, DXCC count, most/least credited groups), but says nothing about data provenance, freshness, or cost of the open-world call.

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?

Two sentences, front-loaded with the purpose and followed by a compact enumeration of return categories. No filler, no restatement of the tool name.

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?

A no-parameter tool with an output schema and full annotation coverage needs little, and the description supplies the only missing piece — the shape of the summary. Minor gap: no note on what population or version of the IOTA programme the statistics reflect.

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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate and it correctly makes no parameter claims.

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?

Specific verb ('Get') plus a clearly scoped resource ('IOTA programme summary statistics'), with the returned fields enumerated. It is obviously distinct from the sibling tools (iota_lookup, iota_search, iota_nearby) which all target individual records rather than aggregate counts, though it never names them 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 is only implied: the word 'summary' signals this is for aggregate/overview needs rather than per-record queries, but there is no explicit statement of when to prefer it over iota_search or iota_islands, and no prerequisites or exclusions are given.

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