Skip to main content
Glama

Route a situation to the right guides and stacks

dp_route
Read-onlyIdempotent

Pick the 1 to 3 situations that fit the user and get the guides and stacks to read for each. Choose the ids yourself from what the user said; never send their words, which stay with you. The standard starting set is always included. Open a result with dp_get_guide or dp_get_stack. For a keyword lookup use dp_search instead. Situations: new-to-privacy (I'm new to privacy and don't know where to start); work-or-business (I work from home or run a business); journalist-or-activist (I report, research or organise); harassment (Someone is watching or harassing me); car-data (My car is sharing how I drive); family-location (I want to share location with my family); leave-google (I want to leave Google); phone (I am choosing or changing my phone); browser (I want a more private browser); accounts (I want better accounts and logins); network (I want to fix my home network or VPN); being-recorded (Someone is recording me); street-cameras (Cameras are watching my street); ai (I want to use AI more privately); smart-tv (My TV is tracking what I watch); clear-online (I want to clear what is already online); start-over (I'm starting over somewhere new).

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": {
      "situations": "<situations>"
    },
    "name": "dp_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
situationsYes1 to 3 situation ids, best fit first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / situations / items / enum
      Previous value: -[
      -  "new-to-privacy",
      -  "work-or-business",
      -  "journalist-or-activist",
      -  "harassment",
      -  "car-data",
      -  "family-location",
      -  "leave-google",
      -  "phone",
      -  "browser",
      -  "accounts",
      -  "network",
      -  "being-recorded",
      -  "street-cameras",
      -  "ai",
      -  "smart-tv",
      -  "clear-online"
      -]New value: +[
      +  "new-to-privacy",
      +  "work-or-business",
      +  "journalist-or-activist",
      +  "harassment",
      +  "car-data",
      +  "family-location",
      +  "leave-google",
      +  "phone",
      +  "browser",
      +  "accounts",
      +  "network",
      +  "being-recorded",
      +  "street-cameras",
      +  "ai",
      +  "smart-tv",
      +  "clear-online",
      +  "start-over"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / situations / items / enum
      Previous value: -[
      -  "work-or-business",
      -  "journalist-or-activist",
      -  "harassment",
      -  "car-data",
      -  "family-location",
      -  "leave-google",
      -  "phone",
      -  "browser",
      -  "accounts",
      -  "network",
      -  "being-recorded",
      -  "street-cameras",
      -  "ai",
      -  "smart-tv",
      -  "clear-online"
      -]New value: +[
      +  "new-to-privacy",
      +  "work-or-business",
      +  "journalist-or-activist",
      +  "harassment",
      +  "car-data",
      +  "family-location",
      +  "leave-google",
      +  "phone",
      +  "browser",
      +  "accounts",
      +  "network",
      +  "being-recorded",
      +  "street-cameras",
      +  "ai",
      +  "smart-tv",
      +  "clear-online"
      +]
  3. Changed3 schema fields changed
    • removedInput schema / properties / situation
      Removed value: -{
      -  "description": "The situation or goal, in the user's own words.",
      -  "maxLength": 500,
      -  "minLength": 2,
      -  "type": "string"
      -}
    • addedInput schema / properties / situations
      Added value: +{
      +  "description": "1 to 3 situation ids, best fit first.",
      +  "items": {
      +    "enum": [
      +      "work-or-business",
      +      "journalist-or-activist",
      +      "harassment",
      +      "car-data",
      +      "family-location",
      +      "leave-google",
      +      "phone",
      +      "browser",
      +      "accounts",
      +      "network",
      +      "being-recorded",
      +      "street-cameras",
      +      "ai",
      +      "smart-tv",
      +      "clear-online"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "situation"
      -]New value: +[
      +  "situations"
      +]
  4. Added

TDQS

A4.8/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior. The description adds important non-obvious context: the privacy rule that the user's words stay with the caller and the fact that the standard starting set is always included. It does not fully describe the response shape, but that is a minor gap for a routing tool.

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 front-loaded with the core action, privacy constraint, routing guidance, and alternative tool before the id list. The long enumeration is justified because each situation id needs a semantic gloss for correct selection.

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?

Given the single parameter, lack of output schema, and router role, the description is complete enough to call correctly. It covers selection behavior, privacy handling, the standard starting set, follow-up tools, and an alternative for keyword search.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already has 100% description coverage, the description adds substantial semantic meaning by mapping every situation id to a plain-language user scenario. This helps the agent choose the correct ids rather than merely reading the enum.

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: pick 1-3 situation ids and return the relevant guides and stacks. It clearly distinguishes this routing tool from dp_search for keyword lookup and from dp_get_guide/dp_get_stack for opening results.

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?

It gives explicit usage rules: choose ids yourself, do not send the user's words, include the standard starting set, and use dp_search instead for keyword lookup. It also names the follow-up tools for opening results, leaving little to inference.

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