Skip to main content
Glama

VPS Hardening

vpshardening__get_ship_digest

Orient on this Ship — ALWAYS call this first. With no arguments it returns the section MAP and nothing else: every top-level section with its description and child_count, which is small and cheap even on a Ship of hundreds of nodes. Then pass { section_id } to list one section's direct children, and vpshardening__read_node for the ones worth reading. A large section arrives in pages — continue it with { cursor }.

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

Input Schema

NameRequiredDescriptionDefault
cursorNo
section_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose non-obvious behavior: the no-argument call returns only the map, the response is cheap even for hundreds of nodes, and large sections are paginated via a cursor. What it omits is the read-only guarantee and what happens with an invalid or unknown section_id.

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?

The description is front-loaded with the routing rule, then explains the no-argument behavior, then explains the drill-down behavior. It is dense but nearly every sentence carries information; 'which is small and cheap even on a Ship of hundreds of nodes' is the only sentence that is more reassurance than fact.

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?

The description covers enough for an agent to call this tool correctly: no-argument versus section_id modes, pagination continuation, and a partial output overview for the map. There is no output schema and no annotations, and the shape of the children listing is unspecified, but the gaps are modest for a 2-optional-parameter read tool.

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 description coverage is 0%, so the description has to explain both parameters. It does say what each parameter means: section_id lists that section's direct children, and cursor continues a paginated section listing. It does not clarify whether cursor can be used without section_id, nor what format the section_id or cursor take.

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?

The description gives a specific verb and resource: it returns a section MAP with each section's description and child_count, and with section_id lists that section's direct children. It also names vpshardening__read_node as the follow-on step. It does not distinguish itself from the sibling vpshardening__list_ship_nodes, which sounds like a near-overlapping listing operation, so an agent may hesitate between the two.

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 a strong entry-point rule ('ALWAYS call this first') and an explicit branching pattern: no arguments for the map, { section_id } to drill in, vpshardening__read_node to read content. It gives no guidance on when to choose search_nodes or list_ship_nodes instead, and no exclusion for any case in which this orientation step can be skipped.

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.