Skip to main content
Glama

BRAINIAC Privacy Operations

Report privacy documentation

privacy-operations_documentation-report
Read-onlyIdempotent

Combine supplied sections, categories, retention periods, notice differences, cookie consent states, request types, and deletion evidence. The report does not determine GDPR compliance. Price $0.12 USDC. POST /api/v1/privacy-operations/documentation-report. 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_documentation-report"
  }
}

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.
cookiesNocookies. Array.
periodsNoperiods. Array.
findingsNofindings. Array.
requestsNorequests. Array.
sectionsNosections. Array.
checkedAtNocheckedAt. String.
categoriesNocategories. Array.
comparisonsNocomparisons. Array.
limitationsNolimitations. Array.
sectionCountNosectionCount. Number.
categoryCountNocategoryCount. Number.
gdprComplianceNogdprCompliance. Boolean.
recordsDeletedNorecordsDeleted. Boolean.
consentEnforcedNoconsentEnforced. Boolean.
legalConclusionNolegalConclusion. Boolean.
recordsAccessedNorecordsAccessed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description is not obligated to repeat safety traits. It instead adds genuinely useful behavior beyond the annotations: the $0.12 USDC price, the POST endpoint, the fact that an unpaid call returns x402 payment terms and does not execute, and the explicit non-determination of compliance. Only the absence of any note on how supplied vs. omitted inputs are treated keeps this below 5.

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?

Four short sentences, each load-bearing: what is combined, what the report is not, what it costs, where it lives, and what an unpaid call does. The scoping caveat is front-loaded immediately after the purpose. No repetition of schema detail.

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?

For a 13-parameter, all-optional, deeply nested tool with an output schema, the description gives an agent enough to decide and invoke: input domain, cost, endpoint, payment failure mode, and the compliance-scope limit. What is missing is any guidance on minimum viable input or how partial inputs affect the report, which matters given every parameter is optional.

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% across 13 parameters, including nested object fields and the mediaType/document/kind enums, so the schema carries the parameter burden. The description names the conceptual inputs (sections, categories, retention periods, consents, evidence, requests) but does not explain how free-form fields like json/text/notice/policy interact or which should be used when. Baseline 3 is appropriate.

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 names a specific action and content scope: it combines supplied sections, categories, retention periods, notice differences, cookie consent states, request types, and deletion evidence into a documentation report. That is far more informative than the title alone. It stops short of explicitly positioning itself against the sibling checks it aggregates (cookie-consent audit, retention check, notice consistency check), which keeps it from a 5.

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?

The essential scoping caveat is present: 'The report does not determine GDPR compliance,' which tells an agent this output is not a compliance verdict. Beyond that there is no when-to-use guidance, no mention of which sibling checks feed it, and no stated prerequisites for the supplied inputs. Usage must largely be inferred from the parameter list.

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