Skip to main content
Glama

Vaultan

Read a page of vaultan.app as Markdown

read_page
Read-onlyIdempotent

Returns the text of one page of vaultan.app as Markdown. Give the path from find_pages, for example "/security/" or "/de/tools/merge-pdf/".

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": {
      "path": "<path>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe page path, starting and ending with "/".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds value beyond them by disclosing the return format (Markdown text) and the single-page scope, which implies no bulk retrieval. It omits what happens for a nonexistent path, a minor gap given the strong annotation coverage.

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?

Two short sentences: the first states what is returned and in what format, the second states how to supply the argument. Nothing is redundant and the core purpose 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?

For a single-parameter read tool with no output schema and full annotation coverage, the description covers purpose, format, and input source adequately. Only edge-case behavior (invalid or missing page) is left unstated, which is a small residual gap rather than a blocker to correct invocation.

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 schema already states the path must start and end with "/", so baseline would be 3. The description earns above baseline by supplying concrete example values ("/security/", "/de/tools/merge-pdf/"), which demonstrate locale-prefixed paths and trailing-slash conventions that the schema alone does not illustrate.

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?

"Returns the text of one page of vaultan.app as Markdown" names a specific verb (returns), resource (one page of vaultan.app), and output format (Markdown). It also implicitly contrasts with find_pages, which enumerates pages rather than fetching one, so an agent can tell the two apart 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?

"Give the path from find_pages" establishes the correct prerequisite workflow: discover paths first, then read. It does not state any when-not-to-use condition or error behavior for an unknown path, but the sequencing guidance is clear and actionable.

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