Skip to main content
Glama

BRAINIAC Privacy Operations

Compare a policy and a notice

privacy-operations_notice-consistency-check
Read-onlyIdempotent

Compare purpose, stated basis, and retention for the same category in a supplied policy and notice. A difference is reported and neither document is chosen. Price $0.05 USDC. POST /api/v1/privacy-operations/notice-consistency-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_notice-consistency-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.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
comparisonsNocomparisons. Array.
limitationsNolimitations. Array.
gdprComplianceNogdprCompliance. Boolean.
recordsDeletedNorecordsDeleted. Boolean.
legalConclusionNolegalConclusion. Boolean.
recordsAccessedNorecordsAccessed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description correctly focuses on traits annotations cannot express: the $0.05 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms and does not execute. That payment-gate behavior is genuinely useful operational context. It stops short of describing output shape or limits, but the output schema covers returns.

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 doing distinct work: purpose, outcome semantics, price, transport, and the payment failure mode. Purpose is front-loaded and nothing is repeated from the annotations.

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 biggest unanswered question is the relationship among the many input channels (free-text/csv/file/json vs structured categories, cookies, consents, evidence, requests, sections) and which are needed for a valid comparison. Output behavior is covered by the output schema, so that omission is acceptable, but the input-selection guidance is a real gap.

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 nominally 100%, hitting the baseline-3 rule, but those descriptions are boilerplate type/length restatements with no semantic meaning. The description only clarifies that policy and notice hold the two documents being compared; it says nothing about how the alternative input channels (csv, file, json, text) or the categories/requirements arrays are used, so 13 parameters remain semantically opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (compare) plus the exact fields compared (purpose, stated basis, retention) and the scope (same category, supplied policy vs notice). This is precise enough that an agent can tell it apart from sibling audits like policy-structure-audit or documentation-report without opening a schema.

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 description makes the operation's intent clear and notes that 'a difference is reported and neither document is chosen,' which implicitly tells the agent this is diagnostic, not remedial. However, it never states when to prefer this over sibling checks, nor what inputs are prerequisite (both documents must be supplied).

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