Skip to main content
Glama

JanuaPort Docs

docs_search

Read-only

Searches the setup guides for a question or a few words (not a single keyword). Returns document key, section heading and a short excerpt per match, best first — fetch the actual text with docs_get. Every answer names the JanuaPort release the guides belong to. Reads only; changes nothing.

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": {
      "frage": "<frage>"
    },
    "name": "docs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
frageYesWhat you want to find — a question or a few words, not a single keyword. Word-level match: a hit needs at least one matching word; ranked by how many words matched.

Output Schema

NameRequiredDescriptionDefault
standYesJanuaPort release these guides belong to.
trefferYesThe matches, best first. Capped. Empty means nothing found — not an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and "Reads only; changes nothing" restates that rather than adding to it. What the description does add is real behavioral context beyond the annotations: best-first ranking, word-level matching, the per-match fields, and the release-scoping note. It stops short of saying how many matches are returned or whether results are truncated.

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?

Three front-loaded sentences with no filler; the retrieval pointer and the version note each earn their place. The only mild redundancy is repeating "not a single keyword," which the schema already states.

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 one fully described parameter, an output schema, and readOnly annotations, the description covers purpose, matching semantics, return shape, and the handoff to docs_get. The one gap is result-set size or truncation behavior, which an agent would want to know before paging or re-querying.

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% and the frage property already documents the word-level match rule and the "not a single keyword" constraint, so the description largely echoes the schema. The matching is reinforced but no new syntax, length, or formatting guidance is added. Baseline 3 applies when the schema carries the parameter burden.

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?

The definition names a specific verb and resource ("searches the setup guides") and immediately distinguishes the scope from the sibling docs_get ("fetch the actual text with docs_get"). An agent can tell from the text alone that this is the discovery step and docs_get is the retrieval step.

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

Usage Guidelines5/5

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

It states the input condition ("a question or a few words (not a single keyword)") and the follow-up condition ("fetch the actual text with docs_get"), explicitly routing to the alternative tool. The constraint against single-keyword queries is a concrete when-to-use rule that prevents a common misuse.

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