Skip to main content
Glama

VPS Hardening

vpshardening__read_node

Read one node's full markdown body + frontmatter by node_id. Response includes outbound_links[] (resolved graph edges) unless with_links:false, plus source attribution. Pass heading (e.g. "Tactics") to get ONLY that markdown section — a few hundred chars instead of the whole body; every heading read, hit or miss, carries the node's headings list, and a miss is heading_not_found — so a guessed heading is cheap (heading "" just lists the headings). A heading read is partial — never write it back as a node's content; re-read without heading first. A long body is returned one page at a time — when the response says truncated, call again with { cursor } to continue it.

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": {
      "node_id": "<node_id>"
    },
    "name": "vpshardening__read_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
headingNo
node_idYes
with_linksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full load and does so: it discloses the outbound_links behavior and the with_links:false switch, source attribution, the headings-list side effect on every heading read, the heading_not_found miss semantics, and that a heading read is partial and must not be written back. It also explains the truncation/cursor pagination loop, which is exactly the kind of behavior an agent would otherwise get wrong.

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?

Purpose and return shape are front-loaded, then heading behavior, then pagination — a sensible order. The em-dash clauses make individual sentences dense and slightly hard to scan, but essentially every clause conveys operational information.

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?

For a four-parameter read tool with no annotations and no output schema, the description covers returns, side effects, error cases, partial-read caveats, and pagination. There is no material gap an agent would need to resolve before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must define all four parameters, and it does: node_id (implicit in the opening), heading with example and empty-string convention, with_links with its default effect, and cursor with the re-call pattern when truncated. No parameter is left for the agent to guess.

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 first sentence names a specific verb and resource (read one node's full markdown body + frontmatter by node_id) and states exactly what is returned. That is enough to distinguish it from list_ship_nodes and search_nodes without opening any 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?

It gives clear situational rules: use heading to fetch a single section cheaply, pass heading "" to list headings, and re-read without heading before writing content back. It does not explicitly contrast with search_nodes or list_ship_nodes, so the family-level routing is left implicit.

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.