Skip to main content
Glama

BRAINIAC Privacy Operations

Classify data subject requests

privacy-operations_data-subject-request-classify
Read-onlyIdempotent

Match a supplied request type to access, deletion, correction, export, objection, or restriction. Any other wording is left unrecognized. No response deadline is calculated. Price $0.03 USDC. POST /api/v1/privacy-operations/data-subject-request-classify. 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-subject-request-classify"
  }
}

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.
requestsNorequests. 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.6/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the taxonomy is closed with no fallback category, deadlines are deliberately not computed, and the paid-call mechanics ($0.03 USDC, x402 terms returned on unpaid calls, no execution) are disclosed. Annotations already cover safety (readOnly/idempotent/non-destructive), so this is meaningful incremental context rather than repetition.

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-loaded with the core operation, then scope exclusions, then cost and transport details. Sentences are short and each carries information; the endpoint string is the only marginally expendable item.

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?

Covers cost, transport, scope limits, and non-behavior, and an output schema exists so return values need not be explained. The gap is input orientation: with 13 optional parameters spanning cookies, consents, categories, and requirements, the description never indicates which one drives the match, leaving an agent to guess how to call it.

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 baseline is 3, but the description adds no mapping between the 13 optional inputs and the classification act — notably it doesn't say that requests[].type (or text) carries the request type being matched, nor whether the requests array enables batch classification. With a schema this broad and largely tangential to the stated purpose, a short pointer would have added genuine value.

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 concrete operation (match a supplied request type) and enumerates the closed target set (access, deletion, correction, export, objection, restriction). That is specific enough that an agent can distinguish this classification step from the sibling audit/check tools, though it never names those siblings explicitly.

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 useful negative scope — 'Any other wording is left unrecognized' and 'No response deadline is calculated' tell the agent what this tool will not do, which implicitly points to other tools for deadline/SLA work. However, there is no explicit when-to-use versus the sibling checks or prerequisites for calling it, so guidance is only implied.

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