Skip to main content
Glama

Default Privacy

by io.github.privatebydefault
OverviewDiscussionsAdmin

Search privacy tools

dp_search_tools
Read-onlyIdempotent

Use when a user wants privacy tool recommendations (VPNs, email, browsers, messengers, password managers, etc.). Matches records containing every query word, so 1–2 keywords such as 'vpn' or 'password manager' work and a full sentence usually returns nothing. For a whole kind of tool, use category instead (slugs from dp_list_categories). Put requirements in the filters; a filter matches only a sourced yes, so with a category it also returns picks_not_checked: that category's picks left out only because the field is unchecked, which the user should still hear about. Returns 10 records by default (up to 50 with limit), ordered DP picks first (in DP's order, within the category if one is given), then A to Z. A record has pick when Default Privacy recommends it as a starting point in a category (null otherwise; not a security guarantee). Records carry jurisdiction, logging, encryption, and dp_url (the record's Default Privacy page). A null field means Default Privacy has not checked it (never read null as no). For sources and caveats call dp_get_tool.

Input Schema

NameRequiredDescriptionDefault
e2eeNoOnly tools Default Privacy has confirmed end-to-end encrypted from a source. Tools it has not checked are left out (see picks_not_checked).
sortNoSort order. Default 'picks': DP picks first, then A to Z. 'ado_score' is a deprecated alias of 'picks'.
limitNoMax results (1–50, default 10).
queryNo1–2 keywords matched against name, tagline, and description; every word must match. E.g. 'vpn', 'email', 'notes'.
offsetNoPagination offset (default 0).
categoryNoCategory slug or name to filter by (see dp_list_categories).
open_sourceNoOnly tools Default Privacy has confirmed open source from a source. Tools it has not checked are left out (see picks_not_checked).
has_free_tierNoOnly tools Default Privacy has confirmed have a free tier. Tools it has not checked are left out (see picks_not_checked).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / e2ee / description
      Previous value: -"Only end-to-end encrypted tools."New value: +"Only tools Default Privacy has confirmed end-to-end encrypted from a source. Tools it has not checked are left out (see picks_not_checked)."
    • changedInput schema / properties / has_free_tier / description
      Previous value: -"Only tools with a free tier."New value: +"Only tools Default Privacy has confirmed have a free tier. Tools it has not checked are left out (see picks_not_checked)."
    • changedInput schema / properties / open_source / description
      Previous value: -"Only open-source tools."New value: +"Only tools Default Privacy has confirmed open source from a source. Tools it has not checked are left out (see picks_not_checked)."
  2. Changed2 schema fields changed
    • removedInput schema / properties / accepts_crypto
      Removed value: -{
-  "description": "Only tools whose crypto payment Default Privacy has checked and confirmed (unchecked tools are not matched).",
-  "type": "boolean"
-}
    • removedInput schema / properties / no_kyc
      Removed value: -{
-  "description": "Only tools Default Privacy has checked and confirmed need no KYC to purchase/use (unchecked tools are not matched).",
-  "type": "boolean"
-}
  3. Changed2 schema fields changed
    • changedInput schema / properties / accepts_crypto / description
      Previous value: -"Only tools that accept cryptocurrency."New value: +"Only tools whose crypto payment Default Privacy has checked and confirmed (unchecked tools are not matched)."
    • changedInput schema / properties / no_kyc / description
      Previous value: -"Only tools that require no KYC to purchase/use."New value: +"Only tools Default Privacy has checked and confirmed need no KYC to purchase/use (unchecked tools are not matched)."
  4. Changed3 schema fields changed
    • removedInput schema / properties / min_ado_score
      Removed value: -{
-  "description": "Minimum ADO listing-quality score (0–100).",
-  "maximum": 100,
-  "minimum": 0,
-  "type": "number"
-}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order. Defaults to highest ADO score first."New value: +"Sort order. Default 'picks': DP picks first, then A to Z. 'ado_score' is a deprecated alias of 'picks'."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "ado_score",
-  "name",
-  "recently_verified",
-  "recently_added"
-]New value: +[
+  "picks",
+  "ado_score",
+  "name",
+  "recently_verified",
+  "recently_added"
+]
  5. Changed2 schema fields changed
    • changedInput schema / properties / min_ado_score / description
      Previous value: -"Minimum ADO composite score (0–100)."New value: +"Minimum ADO listing-quality score (0–100)."
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search over tool name and tagline, e.g. 'vpn', 'email', 'notes'."New value: +"1–2 keywords matched against name, tagline, and description; every word must match. E.g. 'vpn', 'email', 'notes'."
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses matching logic (AND across all query words), default ordering (DP picks first, then A–Z), default page size, the `pick` field meaning, and the critical caveat that null never means 'no' and that unchecked fields produce picks_not_checked. That is substantial behavioral context an agent would otherwise have to guess.

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?

Usage guidance is front-loaded in the first sentence and the paragraph proceeds from query strategy to filters to return shape in a logical order. It is dense and somewhat run-on, but nearly every clause carries operational information.

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 8 optional parameters and no output schema, the description steps in to describe the result shape: default 10 results, up to 50, ordering rules, the `pick` field, jurisdiction/logging/encryption/dp_url fields, and null semantics. An agent can call and interpret this correctly without further docs.

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 semantics: query word-AND matching, category slugs sourced from dp_list_categories, filter behavior ('a filter matches only a sourced yes'), and limit up to 50. It doesn't explain offset/pagination beyond the schema, keeping it at 4 rather than 5.

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 first sentence names a specific verb and resource ('privacy tool recommendations') and enumerates the domain (VPNs, email, browsers, messengers, password managers). It is clearly separable from dp_get_tool (detail) and dp_list_categories (browsing), both of which are named.

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 when-to-use context, plus concrete keyword guidance ('1–2 keywords ... a full sentence usually returns nothing') and names the alternative for browsing a whole kind of tool: `category` with slugs from dp_list_categories. It also routes to dp_get_tool for sources and caveats.

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