Skip to main content
Glama

Get a guide summary

get_guide
Read-onlyIdempotent

Returns one guide by slug: summary, first paragraph, how the procedure is filed (online, representative or in person), validity dates, official source domain, up to five key questions and answers, the date last checked and a link to the full guide. Closed or unconfirmed guides return only their status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the guides: "es" Spanish, "en" English, "uk" Ukrainian. Default: Ukrainian for Cyrillic queries, otherwise English.
slugYesGuide slug from search_guides, e.g. "tie-como-obtener".

Output Schema

NameRequiredDescriptionDefault
langYes
linkYes
slugNo
as_ofNo
staleNo
titleNo
statusNo
summaryYes
age_daysNo
disclaimerYes
verified_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / age_days
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world access. The description adds substantive behavior beyond that: it returns up to five key questions and answers, and closed or unconfirmed guides return only their status. It does not describe not-found or error behavior, so 4 rather than 5.

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 front-loaded with the core action, and the field list is informative rather than filler. The long enumeration is somewhat dense and partly overlaps the output schema, but it remains efficient.

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?

The output schema and annotations carry much of the contract, while the description adds return content and the closed/unconfirmed guide behavior. It is complete enough for a read-only single-item retrieval tool, though not-found handling is left implicit.

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%, and the schema already documents the slug source and the lang enum with its default behavior. The description only says 'by slug' and does not add format or value meaning beyond what the schema provides, so baseline 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 states a specific verb and resource: returns one guide by slug, then enumerates the included content. This clearly distinguishes it from search_guides, which is a search operation rather than single-slug retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The single-guide-by-slug scope and the slug parameter description tying it to search_guides make the intended usage clear. It does not explicitly state when not to use this tool or name search_guides in the description, so it falls short of a 5.

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