Skip to main content
Glama

Read one guide

get_guide
Read-onlyIdempotent

One guide in full: its quick answer, its text as markdown, the day it was last updated, and its address on the site. Takes a slug from list_guides.

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
slugYesThe guide's slug, for example "sell-an-msp".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so the safety profile is covered. The description's real contribution is disclosing the shape of the response (four named fields) in the absence of an output schema. It says nothing about behavior for a missing or invalid slug.

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 sentences, no filler, and the payload description is front-loaded before the input note. Every clause carries information an agent would otherwise have to guess.

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 one-parameter read tool with annotations and no output schema, the description covers both what goes in and what comes back, which is the important part. The only gap is undefined behavior for a nonexistent slug.

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 coverage is 100% and the schema already documents the slug with an example, so the baseline is 3. The description adds only the provenance hint that the slug comes from list_guides, which is a modest but real gain over the schema.

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?

Names a specific verb and resource (read one guide in full) and enumerates exactly what comes back: quick answer, markdown text, last-updated date, and site address. That return-field list also separates it cleanly from list_guides and the other list_* siblings.

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?

States the input's origin explicitly ("Takes a slug from list_guides"), which implies the correct two-step workflow: list first, then fetch. It gives no explicit exclusion or when-not guidance, but no plausible alternative single-guide reader is implied here.

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