Skip to main content
Glama

JanuaPort Docs

docs_get

Read-only

Reads ONE section of a setup guide. Without abschnitt you get the table of contents of the document (with the size of each section) — that is the normal first call; with abschnitt you get that section's text (a section brings its subsections with it). A whole long document is never returned in one answer. Every answer names the JanuaPort release the guide belongs 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": {
      "id": "<id>"
    },
    "name": "docs_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument key, e.g. "inbetriebnahme". Use docs_list if you do not know it.
abschnittNoOptional section heading. Omit it to get the table of contents first — that is the normal first step.

Output Schema

NameRequiredDescriptionDefault
idYesThe document key.
textNoThe section text.
standYesJanuaPort release this guide belongs to.
titelYesTitle of the document.
inhaltNoThe table of contents, when no section was asked for.
abschnittNoThe section that was returned. Empty when this is a table of contents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so 'Reads only; changes nothing' mostly restates them. The description nonetheless adds real behavior beyond the annotations: a whole long document is never returned, the TOC includes section sizes, a section carries its subsections, and every answer names the JanuaPort release.

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?

Four short sentences, front-loaded with the core action and then the default-first-call rule. Nothing is padded and the size/scope constraint is stated before the caveats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation; the description still covers scope limits, call ordering, and release labeling. Nothing an agent needs to invoke this correctly is missing.

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, but the description adds consequence-level meaning: omitting `abschnitt` yields the TOC, supplying it yields that section plus its subsections. This goes beyond the schema's field text, though it partly repeats it.

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 ('Reads ONE section of a setup guide') and precisely describes the two modes: TOC without `abschnitt`, section text with it. It does not explicitly differentiate itself from the sibling tools docs_list or docs_search, which only appear inside the schema, so it stops short of a 5.

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?

Gives explicit workflow guidance: omitting `abschnitt` 'is the normal first call' / 'the normal first step', which tells the agent the correct call order. It offers no when-not guidance and does not name alternatives such as docs_search for content lookup, so it is clear but not complete.

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