Skip to main content
Glama
privacyscrubber-mcp

privacyscrubber-mcp

Get ZTDS Specification & License Capabilities

ztds_info
Read-onlyIdempotent

Retrieve ZTDS RFC v1.0 specification metadata, protocol invariants, baseline entity categories, and local PrivacyScrubber license/profile capability status to verify compliance and masking readiness.

Instructions

Returns ZTDS RFC v1.0 specification metadata, protocol invariants, baseline entity categories, and current local PrivacyScrubber license/profile capability status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ztds_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile needs no restating. The description adds the substantive return content (spec metadata, invariants, entity categories, license status) but says nothing about whether the license/profile portion is live, cached, or scoped to the local host — context that matters for a status-bearing call.

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?

A single sentence, front-loaded with the verb and the resource, with no filler or repetition. The four-item enumeration is dense but each item carries distinct information, so nothing is wasted.

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 zero parameters, no output schema, and annotations covering safety, the description is the only source of return-value information, and it enumerates the returned payload categories adequately. It falls short of 5 only because it does not clarify what "license/profile capability status" concretely means or how current it is.

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?

The tool takes zero parameters, so the baseline is 4; there is no argument meaning the description could add. The stated scope of returned content is sufficient for an agent to know it can call this with no inputs.

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?

Uses a specific verb ("Returns") with a concrete, enumerated resource: ZTDS RFC v1.0 metadata, protocol invariants, baseline entity categories, and local license/profile status. That is far more specific than a tautology, though it never contrasts itself with likely-adjacent siblings such as check_status or guard_session_info, so an agent cannot rule those out from the description alone.

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

Usage Guidelines3/5

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

Usage is only implied by the content list: an agent infers it should call this to learn the protocol spec or check license capability. There is no explicit "use when" statement, no prerequisites, and no named alternative for obtaining license or status information, which is a real gap given siblings like check_status and guard_session_info.

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