Skip to main content
Glama

BRAINIAC Privacy Operations

Check deletion evidence

privacy-operations_data-deletion-evidence-check
Read-onlyIdempotent

Compare supplied deletion requests with supplied evidence lines. A line that says deleted is only a statement in the request. No external record is accessed or deleted. Price $0.04 USDC. POST /api/v1/privacy-operations/data-deletion-evidence-check. An unpaid call returns the x402 payment terms and does not run.

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": "privacy-operations_data-deletion-evidence-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
noticeNonotice, string, length 0 to 200000. Optional.
policyNopolicy, string, length 0 to 200000. Optional.
cookiesNocookies, array. Optional.
consentsNoconsents, array. Optional.
evidenceNoevidence, array. Optional.
requestsNorequests, array. Optional.
sectionsNosections, array. Optional.
categoriesNocategories, array. Optional.
requirementsNorequirements, array. Optional.

Output Schema

NameRequiredDescriptionDefault
checksNochecks. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
gdprComplianceNogdprCompliance. Boolean.
recordsDeletedNorecordsDeleted. Boolean.
legalConclusionNolegalConclusion. Boolean.
recordsAccessedNorecordsAccessed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses three things an agent cannot get from structured fields: the specific conceptual caveat that an evidence line saying 'deleted' is only a claim in the request, the exact price ($0.04 USDC), and the payment-gated behavior (an unpaid call returns x402 payment terms and does not run). That payment gating is materially important for call planning. The read-only/no-external-access claim is consistent with readOnlyHint=true and destructiveHint=false, though there is mild tension with openWorldHint=true.

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 short sentences, purpose front-loaded, then caveat, then cost and transport details, then payment behavior. Nothing is padded. The endpoint path is arguably boilerplate, but it is compact and does not obstruct the key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with nested objects, the description covers purpose, the key semantic caveat, cost, and auth behavior, and an output schema exists so return values need not be explained. What is missing is any signal about how the large set of optional document/consent/policy inputs relate to the evidence comparison, so an agent still has to infer which subset of inputs this check actually consumes.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema itself documents all 13 parameters and the baseline is 3. The description adds meaning for only two of them, tying 'requests' and 'evidence' to the reconciliation task; the other eleven optional inputs (csv, file, json, text, notice, policy, cookies, consents, sections, categories, requirements) are never explained in terms of when or why they matter.

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?

The description gives a specific verb and resource: 'Compare supplied deletion requests with supplied evidence lines.' It also clarifies the semantic nature of the comparison ('A line that says deleted is only a statement in the request'), which tells the agent this is a consistency/attestation check rather than a verification against a live system. It does not explicitly differentiate itself from the sibling audit/check tools, but the purpose is clear enough to select on.

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 implied by the description: use it when you have both a set of deletion requests and a set of evidence lines to reconcile. The scope caveat ('No external record is accessed or deleted') tells the agent what this tool cannot do, which is a useful boundary. However, there is no explicit when-to-use/when-not guidance and no named alternative among the sibling check tools.

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