Skip to main content
Glama

The Landing Company of Madison Park

Read a guide

get_guide
Read-onlyIdempotent

The full text of one guide, by slug from list_guides (a guide’s URL or title also works). Call with no slug to list the guides.

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": "get_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoThe guide’s slug, from list_guides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"The guide’s slug, from list_guides."
    • removedInput schema / required
      Removed value: -[
      -  "slug"
      -]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value on top: it discloses that the return value is the guide's full text and that URL or title identifiers are accepted in addition to the enumerated slugs, which an agent would not learn from the structured fields alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler. The primary behavior and identifier source come first, with the fallback case deferred to the end where it belongs.

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?

One optional enum parameter, no output schema, and the description covers purpose, identifier source, alternate identifier forms, and the no-argument case. Nothing an agent needs in order to call it correctly 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 100% and the enum lists all six valid slugs, so the baseline is 3. The description goes beyond that by stating that a guide's URL or title also works and by explaining what omission of the optional slug means, which are genuine semantic additions not expressible in the schema.

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 — returns the full text of one guide — and names list_guides as the source of the slug, which separates it from the sibling lister. The closing clause ('Call with no slug to list the guides') partially blurs that separation by duplicating list_guides behavior, keeping it just short of a 5.

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?

Makes clear this is the read-one-guide tool and routes the agent to list_guides for slug discovery, plus explains the no-slug fallback. There is no explicit when-not guidance (e.g., preferring get_faq or get_approach for non-guide content), so it stops at a strong 4.

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