Skip to main content
Glama

VPS Hardening

vpshardening__list_ship_nodes

List every node: node_id, title, parent_id, node_type, plus type/description/tags/resource when set. No bodies. This is a flat list of the WHOLE Ship — on a large one it is long and arrives in pages, so pass { cursor } to continue. To navigate rather than enumerate, use vpshardening__get_ship_digest.

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__list_ship_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does real work: it discloses that bodies are excluded ("No bodies"), that results are a flat whole-Ship enumeration, that large ships produce long paginated output, and that the cursor continues it. It stops short of stating the read-only/permission profile or any rate limits, which leaves a small gap for a no-annotation tool.

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?

Field list first, then the "No bodies" caveat, then pagination behavior, then the pointer to the sibling — front-loaded and ordered by decision relevance. Every clause earns its place; nothing is restated from the schema.

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?

Absent an output schema, the description supplies the return shape itself; absent annotations, it supplies the pagination and body-exclusion behavior. For a single-optional-param list tool, an agent has everything it needs to decide to call it and how to page through results.

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% for the single cursor param, so the description must supply meaning — and it does, explaining that paging occurs on large ships and that { cursor } continues it. It does not say where the cursor originates (presumably the prior response) or the terminal condition, so the semantics are strong but not 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?

"List every node" names a specific verb and resource, then enumerates the fields returned (node_id, title, parent_id, node_type, plus optional fields) so the agent knows exactly what it gets. The scope ("flat list of the WHOLE Ship") and the contrast with the digest sibling make it unmistakable against alternatives like search_nodes or read_node.

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 states the condition that selects the alternative explicitly: "To navigate rather than enumerate, use vpshardening__get_ship_digest." That is a direct when-to-use-this vs when-to-use-another rule, not an inference the agent has to make.

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.