Skip to main content
Glama

data_classification

Read-onlyIdempotent

Classify data elements, map them to LGPD, GDPR, PCI DSS, and HIPAA regulation hints, and list handling controls and open questions as a review aid—not legal advice.

Instructions

Classify data elements, map them to regulation hints (LGPD, GDPR, PCI DSS, HIPAA) and list handling controls and open questions. Review aid, not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "system": "<system>",
      "elements": "<elements>"
    },
    "name": "data_classification"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemYes
elementsYes
jurisdictionsNo

Output Schema

NameRequiredDescriptionDefault
kindNo
itemsNo
systemNo
sourcesNo
summaryNo
nextToolsNo
validatedNo
limitationNo
jurisdictionsNo
highestSensitivityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • removedInput schema / properties / elements / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / elements / items / required
      Previous value: -[
      -  "name",
      -  "category",
      -  "purpose",
      -  "sharedWith"
      -]New value: +[
      +  "name",
      +  "category"
      +]
    • changedInput schema / required
      Previous value: -[
      -  "system",
      -  "elements",
      -  "jurisdictions"
      -]New value: +[
      +  "system",
      +  "elements"
      +]
  2. First observedv0.4.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing what the tool produces (regulation hints, handling controls, open questions) and by flagging the important caveat that output is a review aid, not legal advice — something an agent must not omit when relaying results. It does not explain how classification or regulation mapping is determined, so it is not fully transparent.

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?

Two tight sentences: the capability and its outputs are front-loaded, and the scope caveat closes it. There is no redundant restatement of the name or annotations, and every clause carries information.

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 values need not be described. However, this is a nested, bounded-input tool (up to 60 elements, each with category, residency, sharedWith, retentionDays) with zero parameter documentation in the schema, and the description does not compensate for the categories or jurisdictional filtering that determine results. Adequate to know what the tool is for, insufficient to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the semantic load and largely does not: it never explains 'system', the shape of the 'elements' array, or what 'jurisdictions' controls. The regulation list (LGPD, GDPR, PCI DSS, HIPAA) only loosely implies the jurisdictional input, and nothing clarifies the category vocabulary (personal vs. sensitive-personal, financial-card, children) that drives the whole classification.

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?

The description states a specific verb and resource ('Classify data elements') and enumerates the concrete outputs: regulation hints for LGPD/GDPR/PCI DSS/HIPAA, handling controls, and open questions. That is far more than a restatement of the name. It stops short of a 5 because it does not situate itself against any neighboring tool, though no sibling in the list covers data classification directly.

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?

Usage is only implied: it is framed as a 'Review aid,' which suggests calling it during architecture, threat-model, or compliance reviews rather than for runtime enforcement. There is no explicit when-to-use trigger, no prerequisites (e.g., must elements already be inventoried?), and no statement of when an agent should prefer another tool. The 'not legal advice' boundary is a useful scope limit but is not usage routing.

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