Skip to main content
Glama

JanuaPort Docs

docs_list

Read-only

Lists the setup guides this server can show: document key, title and a one-line summary for each. Call this first, then fetch a document with docs_get. To set JanuaPort up, first ask whether it already runs as a container: if not, start with installation (on Mac or Windows, tell the user first that Docker Desktop is for trying it out and a Linux server is recommended for operation); if it does, start with inbetriebnahme. Every answer names the JanuaPort release the guides belong to. Reads only; changes nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
standYesJanuaPort release these guides belong to.
dokumenteYesThe setup guides this server can show, in a fixed order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context beyond that by stating what each list item contains (document key, title, one-line summary) and that every answer names the JanuaPort release, though the final “Reads only; changes nothing” sentence largely repeats the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the list purpose and call order, but it also includes detailed JanuaPort onboarding steps that go beyond invoking docs_list and would be more at home in a workflow guide. Those details are useful, yet they make the description longer and denser than this simple zero-parameter list tool requires.

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?

Given the low complexity, zero parameters, output schema, and read-only annotation, the description covers everything needed: it explains what the list contains, when to call it, and how it relates to docs_get.

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?

The tool takes zero parameters, so there are no parameter meanings for the description to clarify. The baseline for a parameterless tool applies, and the schema is complete.

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 description gives a specific verb and resource: it lists the setup guides the server can show, including the exact fields returned. It also distinguishes this from the fetch step by telling the agent to call this first and then use docs_get.

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 explicitly says to call this tool first and to fetch a document afterward with docs_get. It also supplies concrete routing guidance for JanuaPort setup: check whether the setup already runs as a container, then choose installation or inbetriebnahme based on that answer.

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