Skip to main content
Glama
iota-mcp

iota-mcp

by qso-graph

Iota Search

iota_search
Read-onlyIdempotent

Search IOTA groups and islands by name to find matching references, with duplicate results removed by IOTA number.

Instructions

Search IOTA groups and islands by name.

Searches both group names and individual island names. Results are deduplicated by IOTA reference number.

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": {
      "query": "<query>"
    },
    "name": "iota_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default 25).
queryYesSearch text (e.g., Hawaii, Shetland, Comoro).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context beyond that: it searches across both group and island names and deduplicates results by IOTA reference number, which helps an agent interpret the result set.

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?

Three short sentences with no filler. The core purpose is front-loaded, and the deduplication detail is a compact, useful follow-up.

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?

The tool is simple, the schema is fully documented, annotations are rich, and an output schema exists. The description covers the key domain behavior and result deduplication, though it omits ranking/ordering details that could help interpret search results.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema examples by explaining that the query is matched against both group names and individual island names, which clarifies the semantics of the query parameter.

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 and resource ('Search IOTA groups and islands') and clarifies the search domain (group names and individual island names). It distinguishes itself implicitly from reference-based lookup siblings, but does not explicitly name an alternative tool.

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 phrase 'by name' and the note that both group and island names are searched imply the appropriate use case. However, there is no explicit when-to-use guidance, no exclusions, and no named sibling alternative such as iota_lookup for reference-based retrieval.

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