Skip to main content
Glama

BRAINIAC Privacy Operations

Audit cookie consent configuration

privacy-operations_cookie-consent-configuration-audit
Read-onlyIdempotent

Read cookie purpose, duration, and the consent state supplied by the caller. An optional cookie without an opt-in or opt-out state is reported. Consent is not enforced and the cookie is not classified by law. Price $0.04 USDC. POST /api/v1/privacy-operations/cookie-consent-configuration-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_cookie-consent-configuration-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.
cookiesNocookies. Array.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
gdprComplianceNogdprCompliance. Boolean.
recordsDeletedNorecordsDeleted. Boolean.
consentEnforcedNoconsentEnforced. 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?

Annotations already cover read-only, idempotent, non-destructive, open-world, so safety is settled. The description adds genuinely non-derivable behavior: a $0.04 USDC price, the POST endpoint, x402 payment gating where an unpaid call returns terms without running, and the reporting rule for cookies missing consent state.

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?

Six short front-loaded sentences: what is read, what is reported, what is explicitly not done, then cost and transport. No padding or 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?

Payment and scope behavior are covered and an output schema exists so return values need no explanation. However, for a 13-parameter tool with nested objects and several parallel payload inputs, the description says nothing about which inputs are expected together, which is the main remaining ambiguity.

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%, so the schema already documents all 13 parameters and their nested fields. The description only echoes the cookies fields (purpose, duration, consent) and adds no meaning about how the other payload inputs (notice, policy, evidence, requirements, file) are used.

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: it reads cookie purpose, duration, and caller-supplied consent state, and reports cookies lacking an opt-in/opt-out state. Distinguishable from sibling audits by the cookie-consent subject matter, though the word 'audit' in the name is never translated into what the audit produces.

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?

Gives scope boundaries ('Consent is not enforced and the cookie is not classified by law'), which implicitly tells the agent when this tool is and is not appropriate. It never names or contrasts with a sibling audit, so the agent must infer routing from the subject matter alone.

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