Skip to main content
Glama

list_compliance_controls

Retrieve compliance controls and their current status across 19 regulatory frameworks, with optional framework filtering to review evidence, notes, and gaps.

Instructions

List compliance controls and their current status.

Supports 19 regulatory frameworks: ai_act, gdpr, uk_gdpr, fadp, bdsg, kvkk, pdpl_saudi, appi, dpa_philippines, privacy_act_au, hipaa, ccpa, lfpdppp, pipl, dpdp, lgpd, pipeda, pdpa_singapore, pipa_korea.

Each control has a framework, article, title, status (compliant / partial / non_compliant / not_applicable), optional notes, and an evidence URL.

Use get_compliance_score to get the aggregated compliance percentage.

Args: framework: Filter by regulatory framework key (optional, returns all if omitted).

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": "list_compliance_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on the data side, naming the exact fields returned (framework, article, title, status, notes, evidence URL) and the four status values, but says nothing about pagination, result volume, permissions, or whether the call is read-only.

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?

The purpose is front-loaded and the alternative routing follows immediately. The long framework enumeration is bulky but justified because the schema has no enum, and the 'Args:' block is small and relevant.

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

Completeness4/5

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

With no output schema, the description correctly takes on the job of describing the returned record shape and status vocabulary. It is nearly complete for a simple list tool, with the main remaining gap being pagination or result-size behavior.

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 is 0% and the schema only declares an unconstrained string, so the description must compensate. It does so by listing all 19 valid framework keys and stating that the parameter is optional with an all-frameworks default, though it does not specify matching behavior for unrecognized keys.

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 and resource plus its scope ('controls and their current status'), and explicitly separates itself from get_compliance_score, which handles the aggregated percentage. An agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to get_compliance_score when an aggregate percentage is wanted, and states that omitting the framework filter returns all frameworks. It does not address other siblings such as list_compliance_reports or update_compliance_control, but the primary when-to-use condition is clear.

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

Deploy Server

Other Tools