Skip to main content
Glama

Get one privacy stack

dp_get_stack
Read-onlyIdempotent

Fetch one privacy stack by slug. Most stacks come back whole in this one call. A long stack returns its summary and its layers with the tools in each, in setup order, instead; then pass section (a layer heading) for why each tool and the tradeoffs, or full: true for the whole stack. Slugs come from dp_list_stacks or dp_search.

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_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the whole stack's markdown (long; prefer section).
slugYesStack slug, e.g. 'privacy-starter-kit', 'degoogle-android-phone'.
sectionNoA layer heading from sections, to return just that part.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / full
      Added value: +{
      +  "description": "Return the whole stack's markdown (long; prefer section).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / section
      Added value: +{
      +  "description": "A layer heading from sections, to return just that part.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover read-only/idempotent safety, so the bar is lower, but the description still adds real value by disclosing the two response modes: whole stack for most, summary plus layers with tools in setup order for long stacks. It does not cover failure behavior for an unknown slug, which keeps it off a 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?

Four front-loaded sentences with no filler: purpose, default return shape, fallback shape, then parameter routing. The phrase 'its summary and its layers' is slightly dense on first read but each sentence earns its place.

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?

No output schema exists, so the description must carry return-shape burden and does: it distinguishes full versus truncated responses, gives the ordering of layers, and explains the two follow-up parameters. Nothing an agent needs in order to call this 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%, so the baseline is 3; the description goes beyond it by tying 'full: true' to the long-stack fallback and explaining that 'section' takes a layer heading from the returned sections. That adds operational meaning the schema only states tersely.

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?

States a specific verb and resource ('Fetch one privacy stack by slug') and immediately distinguishes itself from the sibling list/search tools by naming where slugs come from. An agent can tell this apart from dp_list_stacks or dp_search without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: get slugs from dp_list_stacks or dp_search, and after a truncated response choose between 'pass section' or 'full: true'. This is an explicit when/when-next with named alternatives, not implied usage.

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