Skip to main content
Glama

VPS Hardening

vpshardening__get_blueprint_overview

Read the human-AUTHORED overview prose for the Ship (omit node_id) or for one section. Useful only where someone has written a summary; it is not the way to navigate — vpshardening__get_ship_digest is the map, call that first. When no summary has been written this falls back to the same section map vpshardening__get_ship_digest returns, drilled with { section_id } and paged 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_blueprint_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
node_idNo
section_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the load well: it discloses the fallback behavior when no prose exists (returns the same section map as get_ship_digest, drilled via section_id and paged via cursor). It leaves out error behavior, permissions, and return shape specifics, but the fallback disclosure is the key non-obvious trait.

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?

Three sentences, front-loaded with purpose and the sibling redirect before the fallback detail. Dense and mostly waste-free, though the final sentence packs several behaviors together and takes a second read to parse.

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?

Given no annotations, no output schema, and 0% schema coverage on three parameters, the description covers purpose, routing, fallback, drilling, and pagination — enough for an agent to call it correctly. Nothing important for correct invocation is missing.

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 0%, so the description must compensate, and it largely does: omitting node_id selects the Ship-level overview, section_id drills into a section, and cursor pages results. It adds real meaning beyond the bare property names, though it does not clarify value formats or what happens if node_id is supplied without a matching section.

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?

"Read the human-AUTHORED overview prose for the Ship (omit node_id) or for one section" gives a specific verb, resource, and two scoping modes, and explicitly contrasts itself with vpshardening__get_ship_digest as the navigation tool. An agent can distinguish this from the map/digest sibling without opening a schema.

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 when to use it (only where someone has written a summary), when not to ("not the way to navigate"), and names the exact alternative to call first (get_ship_digest). That is a complete routing rule with explicit exclusions.

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.