Skip to main content
Glama

VPS Hardening

vpshardening__search_nodes

Search nodes by text, node_type, and/or semantic type. Token-AND across title + description + tags. Primary retrieval path — use it before reading bodies. Results are ranked best match first — score on each row is the match strength (title hits count double). Page 1 is the top of the ranking. A one-word query can match hundreds of rows — put two or more terms in query so the top rows are the answer, not a dump. Terms are AND-ed: if two return nothing, drop one. Reports total_matches; when more matches exist than fit in one response, narrow the query or pass { cursor } for the next page (a cursor is only valid for the query that produced it).

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

Input Schema

NameRequiredDescriptionDefault
typeNo
queryNo
cursorNo
node_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it discloses ranking order (best match first), scoring mechanics (title hits count double), AND-ed term semantics, total_matches reporting, and the critical cursor constraint that a cursor is only valid for the query that produced it. That is exactly the kind of non-obvious behavioral context an agent needs to avoid broken pagination.

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?

Front-loads what the tool does and its role as primary retrieval, then layers ranking, query advice, and pagination in a logical order. It is dense but nearly every sentence carries actionable guidance; the query-length advice is slightly repetitive with the "one-word query can match hundreds of rows" clause.

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 search tool with no output schema, the description covers scoring, total_matches, and cursor handling well. It never says what a result row actually contains beyond `score` — whether it's an id/title/snippet or a full node — which matters for deciding whether to follow up with read_node.

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 must compensate, and it largely does — it explains query term behavior (token-AND, multi-term recommendation), the cursor's validity scope, and that `type` is a semantic filter atop `node_type`. It stops short of clarifying how `node_type` differs from semantic `type` or what values either accepts, leaving a real ambiguity between two similarly named filters.

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?

States a specific verb and resource (search nodes) plus the three filter dimensions it accepts, and implicitly separates itself from body-reading tools via "Primary retrieval path — use it before reading bodies." It doesn't name or contrast the sibling list tools, so the differentiation is contextual rather than explicit.

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?

Gives explicit when-to-use ("use it before reading bodies"), how to query well ("put two or more terms in `query`"), a recovery rule ("if two return nothing, drop one"), and a pagination-vs-narrowing decision ("narrow the query or pass { cursor }"). These are concrete alternatives and conditions rather than implied guidance.

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.