Skip to main content
Glama

myIO Documentation

Search myIO docs

myio_search
Read-onlyIdempotent

Keyword search in the myIO documentation (manual, API reference, FAQ, product data). The content is in Hungarian: Hungarian keywords match best, and matching ignores accents and Hungarian word endings. Returns section ids, URLs, version marks and a snippet; myio_read returns the full section.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 6)
queryYesKeywords, preferably in Hungarian, e.g. "redőny időzítő" (blind timer) or "MQTT Home Assistant"
sourceNoRestrict to one source

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing matching behavior (accent- and Hungarian word-ending-insensitive), the content language and its effect on result quality, and the shape of the response (section ids, URLs, version marks, snippet). This is exactly the query-formulation context annotations cannot carry.

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 tight sentences, each with a distinct job: what it searches, how to phrase queries, and what comes back plus the follow-up tool. No filler and the resource scope is front-loaded.

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 no output schema, the description correctly shoulders the burden of describing return fields and the follow-up call, and the language note is essential for a Hungarian corpus. Minor gaps remain around result capping (limit max 15) and what the source values mean, though the schema partly covers these.

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, and the description earns an increment by explaining how keyword matching actually behaves (accents and Hungarian suffixes ignored), which guides query construction. It does not add anything about limit semantics or the source enum values beyond the schema.

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?

Names a specific verb and resource ("keyword search in the myIO documentation") and enumerates the covered content types (manual, API reference, FAQ, product data). It also names the sibling it is not (myio_read) and what that sibling returns, so an agent can distinguish the two without opening either schema.

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?

Explicitly routes the agent: search here for keywords, and use myio_read when the full section is needed. It does not address when to prefer browsing (myio_toc) or product overview (myio_about) over keyword search, so the guidance is clear but not exhaustive.

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