Skip to main content
Glama

Default Privacy

by io.github.privatebydefault
OverviewDiscussionsAdmin

Get one guide

dp_get_guide
Read-onlyIdempotent

Fetch one guide by slug. By default returns its summary, its section headings and its short checked FAQ answers, not the whole text. Pass section (one of the headings) to get that section's text, or full: true for the whole 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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and openWorldHint false. The description adds useful behavioral detail about the default summarized response versus section text versus full markdown, though it does not describe error behavior for invalid slugs.

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?

The description is three concise sentences, front-loads the core operation, and every sentence adds useful information about output modes.

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?

With no output schema, the description clearly explains what is returned by default and how section/full alter the response. Combined with annotations covering the safety profile, it gives enough context to call the tool correctly.

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 schema already documents all three parameters. The description still adds meaning by explaining that section should be one of the provided headings and that full overrides the default summary-only behavior.

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: fetch one guide by slug. The phrase 'one guide' also implicitly distinguishes single-guide retrieval from sibling search tools such as dp_search_guides.

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?

It clearly explains the default behavior and how to request a section or the full guide. It does not explicitly name dp_search_guides as the way to discover a slug, so it lacks full when-to-use routing but provides clear operational context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Default Privacy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources