Skip to main content
Glama

Get one guide

dp_get_guide
Read-onlyIdempotent

Fetch one guide by slug. Most guides come back whole in this one call. A long guide returns its summary, section headings and short checked FAQ answers instead; then pass section (one of the headings) for that section's text, or full: true for the whole guide.

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

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the whole guide's markdown (long; prefer section).
slugYesGuide slug, e.g. 'remove-name-from-data-brokers'.
sectionNoA heading from the guide's sections, to return just that section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / full
      Added value: +{
      +  "description": "Return the whole guide's markdown (long; prefer section).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / section
      Added value: +{
      +  "description": "A heading from the guide's sections, to return just that section.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Guide slug, e.g. 'anonymous-llc-wyoming'."New value: +"Guide slug, e.g. 'remove-name-from-data-brokers'."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive safety profile, so the bar is lower. The description adds genuinely useful behavior beyond annotations: it discloses that responses are sometimes truncated (summary + headings + short FAQ answers) and how to recover the full content.

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?

Three tight sentences, front-loaded with the primary action, followed by the truncation caveat and the recovery options. No filler.

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?

With no output schema, the description usefully characterizes the return shape (whole guide vs. summary/headings/FAQ) and the escalation path. It doesn't mention error behavior for an unknown slug, a minor gap for a 3-parameter lookup tool.

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%, so the baseline is 3, but the description adds real value by explaining the relationship between parameters: section takes 'one of the headings' returned by the truncated call, and full:true is the alternative escalation path. That relational meaning isn't 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 — 'Fetch one guide by slug' — which is clearly distinguishable from the sibling dp_search_guides (plural, search-based). It does not explicitly name the sibling, so it falls just short of full differentiation.

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?

Gives clear operational guidance for the fallback path: if a long guide returns only summary/headings, use section or full:true. It doesn't say when to prefer this over dp_search_guides, but the 'one guide by slug' framing implies it.

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