QR Suisse documentation

Read a QR Suisse documentation page

qr_suisse_get_page

Read-onlyIdempotent

Returns the full Markdown text of one page of the QR Suisse documentation (English), from a closed list: llms-txt, agents-md, auth-md, pricing-md, or api/ for an operation of the QR Suisse REST API v1.

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": {
      "page": "<page>"
    },
    "name": "qr_suisse_get_page"
  }
}

Input Schema

Name	Required	Description	Default
`page`	Yes	Page identifier, as returned by qr_suisse_search_docs.

Output Schema

Name	Required	Description
`url`	Yes	Public address of the document.
`page`	Yes
`title`	Yes
`content`	Yes	Markdown text of the page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the description only needs to add context — and it does: the content is English Markdown, the page set is closed, and api/<operationId> addresses REST API v1 operations. It does not mention pagination or truncation, but for a static doc fetch that is a minor gap.

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?

One front-loaded sentence with no filler; the purpose and scope come first. It partially restates the schema's enum values, which is slight redundancy, but the restatement is short and helps an agent recognize the page set at a glance.

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 one-parameter read tool with an output schema, the description covers what is returned (full Markdown text), the language, and the valid page namespace. Only the discover-then-fetch workflow is left implicit, which is a small remaining gap.

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% and the enum already lists valid values, so baseline is 3. The description adds real meaning by explaining that the enum members are documentation pages and that the api/ prefix maps to a REST API v1 operationId — a convention the raw enum does not convey.

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?

States a specific verb and resource ('Returns the full Markdown text of one page of the QR Suisse documentation') plus the exact scope (English, closed page list). An agent can tell this is a single-page fetch rather than a search, without opening the schema.

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 closed page list and the schema note that identifiers come from qr_suisse_search_docs imply the discover-then-fetch flow, but the description never says when to use this instead of the search sibling or what to do if the page is unknown. Usage is implied, not stated.

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

All QR Suisse documentation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?