Skip to main content
Glama

BRAINIAC Privacy Operations

Extract a personal data inventory

privacy-operations_personal-data-inventory-extract
Read-onlyIdempotent

Copy categories, purposes, stated legal bases, and retention periods from Category fields. Prose is not mined for categories, and a stated basis is not assessed. Price $0.04 USDC. POST /api/v1/privacy-operations/personal-data-inventory-extract. 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_personal-data-inventory-extract"
  }
}

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
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
categoriesNocategories. Array.
limitationsNolimitations. Array.
gdprComplianceNogdprCompliance. Boolean.
recordsDeletedNorecordsDeleted. Boolean.
legalConclusionNolegalConclusion. Boolean.
recordsAccessedNorecordsAccessed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, openWorld), the description discloses the commercial and access behavior an agent cannot otherwise know: a fixed price of $0.04 USDC, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. Those are exactly the operational facts that prevent wasted or failed invocations.

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, front-loaded with the capability and scope limits, followed by cost, transport, and payment-failure behavior. No filler and no restatement of the title.

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?

An output schema and rich annotations exist, so the description needn't explain returns or safety, and it covers the non-obvious payment gating well. For a 13-parameter tool with zero required fields it would be more complete if it stated which input slots are needed or what happens when none are supplied.

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 technically 100%, but the schema descriptions are boilerplate ('name, string, length 1 to 160'), so the description carries real semantic weight by identifying which category fields are actually harvested (basis, purpose, retention) and by implicitly telling the agent that the free-text inputs are handled differently. It still says nothing about the file/json/csv/text input slots or the requirements array, which is why it falls short of a 5.

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 verb ('Copy') and the exact resource content (categories, purposes, stated legal bases, retention periods from Category fields), so the agent knows this is a structured extraction, not an audit. It does not name or contrast any sibling tool such as notice-consistency-check or policy-structure-audit, so differentiation relies on the agent's own reading of the sibling list.

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

Usage Guidelines4/5

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

'Prose is not mined for categories' and 'a stated basis is not assessed' are genuine usage boundaries: they tell the agent this tool is for already-structured category data and that it will not do prose mining or legal-basis evaluation. What's missing is an explicit pointer to the alternative tool to use when the input really is unstructured prose.

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