Skip to main content
Glama

Read a VeteranHQ guide

get_guide
Read-onlyIdempotent

Use this when a slug from search_guides names the guide a veteran needs and the answer should carry what the guide says. Returns the slug, title and summary, the date the facts in it were last verified against its sources, the public URL of the guide on veteranhq.app, the body split into the sections the guide itself defines, each with a heading and its text, and the sources the guide cites, each with a title and a URL. A slug this library does not hold returns a tool error carrying GUIDE_NOT_FOUND, whose message says to call search_guides and use a slug from its results. A guide longer than one result can carry returns the sections that fit, plus omittedSections counting the sections left out and a note stating that count and the guide URL. A single section larger than the whole budget is served shortened at a paragraph or sentence boundary, with truncatedSection naming its heading and the note repeating it, so a section that was cut is distinguishable from one served whole. Those three fields are absent when the whole guide is returned, so a shortened answer is distinguishable from a complete one. A guide states the rules as VeteranHQ read them from the cited sources on the date it reports, and VA decides a claim. It reads no account data, so the answer is the same for every caller with the same inputs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe guide to read, as returned in the slug field by search_guides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the annotations. It discloses truncation behavior (omittedSections, truncatedSection, note), how to distinguish a shortened answer from a complete one, that the tool reads no account data, and that the guide states rules as read from sources on a verification date. It also explains the GUIDE_NOT_FOUND error behavior. This is rich behavioral context that annotations alone do not provide.

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 long but information-dense, covering return fields, truncation behavior, error handling, and scope limitations. It is front-loaded with the primary use case and then details edge cases. It could be slightly more concise, but every sentence earns its place by conveying behavior an agent needs to know.

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?

For a read-only tool with one parameter, no output schema, and no nested objects, the description is remarkably complete. It covers the return payload, error behavior, truncation semantics, and the tool's scope (no account data). An agent has everything needed to invoke it correctly and interpret its 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?

The schema already describes the single parameter (slug) with 100% coverage, so the baseline is 3. The description adds value by explaining that the slug must come from search_guides results and that an invalid slug produces a GUIDE_NOT_FOUND error. This is meaningful context beyond the schema's field description, so a 4 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 opens with a specific verb ('read') and resource ('a VeteranHQ guide'), and immediately ties it to a sibling ('search_guides') by stating the slug comes from there. It clearly distinguishes this tool from the other siblings, which are about calculations, searches, and legal authority, not reading a guide's content.

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?

The description explicitly states when to use this tool: when a slug from search_guides names the guide a veteran needs and the answer should carry what the guide says. It also names the alternative (search_guides) and explains the error path when a slug is not found, telling the agent to call search_guides and use a slug from its results. This is explicit routing 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.

Resources