Skip to main content
Glama
iota-mcp

iota-mcp

by qso-graph

Get Version Info

get_version_info
Read-onlyIdempotent

Retrieves the running service version and IOTA programme data revision so agents can compare MCP deployments and detect version drift.

Instructions

Get iota-mcp service version and upstream programme data version.

Returns the running PyPI version of iota-mcp and the IOTA programme data revision in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: the operation is a lightweight, MCP-protocol-internal check suitable for cross-server drift comparison, which tells an agent it needs no external IOTA API round-trip.

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?

Purpose is front-loaded in the first clause, and the second paragraph gives the operational rationale. There is mild redundancy between 'iota-mcp service version and upstream programme data version' and the restatement as 'running PyPI version ... and IOTA programme data revision in use', but nothing wasteful overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, read-only version probe with full annotations and an output schema, the description supplies everything needed: what is returned, why an agent would call it, and that it stays within the MCP protocol.

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-parameter tool with 100% schema coverage, so the baseline is 4. The description usefully identifies the two outputs (service_version, spec_version) even though the output schema already documents them.

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?

States a specific verb and resource ('Get iota-mcp service version and upstream programme data version') and names the two returned fields, which no sibling tool (iota_lookup, iota_search, etc.) offers. An agent can immediately separate this diagnostics call from the data-lookup siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete use case: confirm fleet alignment across MCP deployments and compare service_version/spec_version to detect drift. It does not explicitly exclude scenarios or name an alternative tool, but for a zero-argument diagnostic the context is clear enough to select it correctly.

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