Skip to main content
Glama

BRAINIAC Privacy Operations

Check stated retention periods

privacy-operations_data-retention-policy-check
Read-onlyIdempotent

Read retention periods stated by the caller. A period counts only as days, months, years, account lifetime, or until deletion. Months are not converted to days, and no statutory period is invented. Price $0.04 USDC. POST /api/v1/privacy-operations/data-retention-policy-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-retention-policy-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
statusNostatus. String.
periodsNoperiods. Array.
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.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing commercial and gating behavior: $0.04 USDC per call, the POST endpoint, and that an unpaid call returns x402 payment terms without executing. It also declares validation policy (months not converted to days, no statutory period invented), which is real behavioral context. It does not describe return values, but an output schema exists.

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?

Tight and front-loaded: purpose first, then unit rules, then pricing, endpoint, and payment-failure behavior. Every sentence carries distinct information with no restatement of the title.

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?

Strong on validation rules and payment mechanics, but thin for a tool with 13 optional nested inputs. An agent gets no guidance on which input channel to choose or what the requirements/categories structures should contain, which matters for a zero-required-parameter tool where input selection is entirely on the caller.

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% with 13 optional parameters, so the schema already documents each field. The description adds nothing about which inputs to prefer (csv vs file vs json vs text) or what categories, requirements, and sections are used for, so it stays at baseline.

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?

States a specific verb and resource: 'Read retention periods stated by the caller,' and the unit rules sharpen what counts as a period. It does not distinguish this tool from near siblings such as policy-structure-audit or notice-consistency-check, so an agent must infer the boundary from the name 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 — an agent can infer this is the tool for validating stated retention periods. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for adjacent tasks like policy structure auditing.

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