Skip to main content
Glama
OjasKord

Data Compliance Classifier MCP

by OjasKord

validate_data_safety_lite

Quickly screens high-volume payloads for sensitive patterns without AI. Returns SAFE_TO_PROCESS or REVIEW_REQUIRED in under 100ms to determine if full classification is needed.

Instructions

Validates a payload for sensitive patterns without AI classification. Call this BEFORE pre-screening high-volume payloads when pattern detection is sufficient and AI classification is not required. Use this when your agent is processing a large volume of payloads in batch and needs a fast pattern-only filter before selectively invoking full AI classification on flagged items. Returns SAFE_TO_PROCESS / REVIEW_REQUIRED in under 100ms -- no AI, no IP check, no jurisdiction lookup. Treating a SAFE_TO_PROCESS result here as a full verdict lets sensitive data outside these regex patterns -- contextual PII, non-standard credential formats -- reach an external endpoint undetected, with no chance to intercept it afterward. Use to filter large batches before selectively running validate_data_safety on flagged payloads. Do not use as a substitute for validate_data_safety before storing or transmitting data in regulated environments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoOptional: what your agent plans to do with this data.
payloadYesThe data payload to screen for sensitive patterns.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
verdictYes
checked_atYes
_disclaimerYes
agent_actionYes
analysis_typeNo
patterns_detectedNo
sensitivity_levelNo
Behavior5/5

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

No annotations provided, so description fully discloses behavioral traits: <100ms, no AI, no IP check, no jurisdiction lookup. Warns that SAFE_TO_PROCESS result can miss contextual PII and is not a full verdict.

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?

Slightly long but every sentence earns its place. Front-loaded with core purpose and usage. No fluff. Could be slightly tighter but still well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values not required but description mentions outputs SAFE_TO_PROCESS/REVIEW_REQUIRED. Also explains risk of false positives. Complete given complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100%, baseline 3. Description adds context for 'context' parameter and explains purpose of 'payload'. Adds value beyond schema descriptions.

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?

Clearly states tool validates payloads for sensitive patterns without AI classification. Distinguishes from sibling 'validate_data_safety' which presumably uses AI. Specific verb 'validate' and resource 'payload'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (pre-screening high-volume payloads when pattern detection sufficient) and when not (regulated environments). Directs to alternative validate_data_safety for flagged items.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OjasKord/data-compliance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server