Skip to main content
Glama
iota-mcp

iota-mcp

by qso-graph

Iota Islands

iota_islands
Read-onlyIdempotent

List all islands and subgroups for an IOTA group by reference number, returning the full hierarchy of subgroups containing individual islands.

Instructions

List all islands and subgroups in an IOTA group.

Returns the full hierarchy: subgroups containing individual islands.

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": {
      "refno": "<refno>"
    },
    "name": "iota_islands"
  }
}

Input Schema

NameRequiredDescriptionDefault
refnoYesIOTA reference number (e.g., NA-005, EU-005).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so safety is covered. The description adds that results come back as a nested hierarchy (subgroups containing islands), which is useful shape information, but says nothing about depth, ordering, or empty results.

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?

Two short sentences, front-loaded with the action and scope, with no wasted filler. The second sentence is mildly redundant with the first but does add the nesting detail.

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 annotations covering the safety profile and an output schema present, the description needn't explain return values. What it provides—action, scope, and hierarchy shape—is sufficient for an agent to call this correctly; only the relationship to sibling lookup tools is left implicit.

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 parameter with 100% schema description coverage, and the description adds no further meaning about the refno format or constraints beyond what the schema provides. Baseline 3 for full schema coverage with no added parameter context.

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 names a specific verb (List) and resource (islands and subgroups in an IOTA group) and clarifies the returned structure as a hierarchy. It is clearly distinguishable from siblings like iota_lookup or iota_stats, though it does not explicitly name those alternatives to sharpen the distinction.

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: an agent can infer you call this when you need the island/subgroup breakdown for a group identified by refno. There is no explicit statement of when to prefer this over iota_lookup or iota_search, and 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.