Skip to main content
Glama

Search the VeteranHQ guides

search_guides
Read-onlyIdempotent

Use this when a veteran asks about a VA topic VeteranHQ has written a guide on. It searches only the VeteranHQ guide library and reads no account data, so the answer is the same for every caller with the same inputs. Returns the guides whose text matches the query, highest scoring first, each carrying the guide slug, title, summary and public URL, and no body text. The ordering is lexical and deterministic, computed from where each word of the query appears: a match in the guide title scores above one in the summary, a summary match above one in a section heading, and a heading match above one in the body, with an added score when every word of the query appears somewhere and a further one when the whole query appears in a title. Guides tied on score are ordered by slug, so the same query returns the same list in the same order on every call. No model runs and no network call is made. The limit parameter caps how many guides come back, from 1 to 10, default 5. An empty results array means no guide in this library contains any word of the query, which is a fact about the library and not about VA rules or about what VA holds. Reading one is a second call: pass a returned slug to get_guide.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many guides to return, 1 to 10. Default 5.
queryYesWhat the veteran is asking about, in keywords or a short phrase, for example "C&P exam" or "how do I get my military medical records".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), yet the description adds substantial non-obvious behavior: deterministic lexical scoring, the title > summary > heading > body precedence, tie-breaking by slug, no model or network call, and what an empty results array does and does not mean. This is context an agent cannot infer from the annotations.

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 purpose and the two-call pattern are front-loaded before the scoring detail, and nearly every sentence carries information. It is slightly redundant, restating determinism ('the ordering is lexical and deterministic' and later 'the same query returns the same list in the same order on every call').

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?

There is no output schema, so the description carries the return burden and does: slug, title, summary, public URL, ordering, and the absence of body text. Nothing an agent needs to call this tool correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already fully documented, including the limit range and default. The description restates the 1-to-10 range and default 5 without adding syntax or format guidance beyond the schema, so the baseline of 3 is appropriate.

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 description names a specific verb and resource ('searches only the VeteranHQ guide library') and states the trigger condition ('when a veteran asks about a VA topic VeteranHQ has written a guide on'). It also distinguishes itself from the sibling get_guide by describing search as the first of a two-call pattern.

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?

Explicit when-to-use is given, plus an explicit boundary (guide library only, no account data), plus the alternative path: read a result by passing a returned slug to get_guide. An agent knows both when to pick this tool and what to do next.

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.

Resources