Skip to main content
Glama

myIO Documentation

myIO table of contents

myio_toc
Read-onlyIdempotent

Table of contents of the myIO documentation: every section id with its title and size. Optional filters: source (manual, api, faq, products, site) and text contained in the section title.

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

Input Schema

NameRequiredDescriptionDefault
filterNoOnly sections whose title contains this text
sourceNoOnly this source

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the return shape: section ids, titles, and sizes. That is genuinely useful given there is no output schema. It does not discuss ordering or pagination, which keeps it short of a 5.

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 what the tool returns, followed by the optional filters. No filler and nothing buried.

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 two-optional-parameter listing tool with no output schema, the description adequately conveys both the return contents and the filter surface. Only minor gaps remain, such as result ordering or what 'size' measures.

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?

Schema coverage is 100%, so both parameters are already documented. The description restates the source enum values and the title-substring filter rather than adding syntax, matching rules, or edge-case behavior, so it sits at the baseline.

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 the concrete resource (the myIO documentation table of contents) and the payload returned (every section id with title and size). That is specific enough to distinguish it from myio_read or myio_search, though it never explicitly contrasts itself with those siblings.

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 description frames the tool as a full TOC with optional narrowing filters, which implies the browse-then-read workflow, but it never says when to prefer this over myio_search or that it should be called before myio_read. Usage must be inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources