Skip to main content
Glama

BRAINIAC Privacy Operations

Audit privacy policy structure

privacy-operations_policy-structure-audit
Read-onlyIdempotent

List headings and Section lines in a supplied policy and compare them with the sections the caller marks as required. Headings are still listed when a required section is absent. A missing section is a gap in the document, not a legal conclusion. Price $0.04 USDC. POST /api/v1/privacy-operations/policy-structure-audit. 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_policy-structure-audit"
  }
}

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.
sectionsNosections. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
requirementsNorequirements. Array.
gdprComplianceNogdprCompliance. Boolean.
recordsDeletedNorecordsDeleted. Boolean.
legalConclusionNolegalConclusion. Boolean.
recordsAccessedNorecordsAccessed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Goes well beyond the annotations: states the output edge case (headings are still listed when a required section is absent), scopes the result as a documentary gap rather than a legal finding, and discloses operational behavior the annotations cannot carry — $0.04 USDC price, POST endpoint, and that an unpaid call returns x402 payment terms without executing. That payment-gating disclosure is exactly the kind of behavior an agent needs before invoking.

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?

Front-loads the core action and the absent-section edge case, then tacks on transport/pricing facts. Five short sentences with no filler, though the price and endpoint sentences read as boilerplate rather than tool-selection content.

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?

An output schema exists, so return-value explanation is rightly omitted, and the payment behavior is covered. But for a 13-parameter, nested-object tool the description only accounts for two inputs; an agent cannot tell from the text why cookies, consents, evidence, requests, or categories are accepted by a structural audit.

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 coverage is 100%, so the baseline is 3; the description adds real meaning only for the `sections` parameter (it holds the sections the caller deems required) and implies the document arrives via one of the text/policy/csv/json/file inputs. The other ten parameters (cookies, consents, evidence, requests, categories, requirements) are left entirely to the schema, unexplained in the description.

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?

Names a concrete verb pair (list headings/Section lines, compare against caller-marked required sections) and a specific resource (a supplied privacy policy). An agent can distinguish it from notice-consistency-check or data-retention-policy-check, though the description never names a sibling to sharpen the boundary.

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?

Implies usage through 'a supplied policy' and 'the sections the caller marks as required,' and adds a useful interpretive rule ('a gap in the document, not a legal conclusion'). However there is no explicit when-to-use / when-not-to-use statement, no prerequisite besides payment, and no routing to the other privacy-operations audits.

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