Skip to main content
Glama

update_compliance_control

Update a compliance control's status, notes, or evidence URL across AI Act, GDPR, HIPAA, and other frameworks; every change is audit-logged.

Instructions

Update the status, notes or evidence URL of a compliance control.

Works across all frameworks (AI Act, GDPR, PDPL, HIPAA, etc.). Write operation — recorded in the audit log.

Args: control_id: UUID of the control to update (from list_compliance_controls). status: New compliance status — one of: compliant, partial, non_compliant, not_applicable. notes: Free-text justification or implementation notes (optional). evidence_url: URL to supporting evidence document or test report (optional).

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": {
      "control_id": "<control_id>",
      "status": "<status>"
    },
    "name": "update_compliance_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
statusYes
control_idYes
evidence_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does disclose that this is a write operation recorded in the audit log, which is useful non-obvious context. It omits required permissions, error behavior for unknown control_id, whether omitted fields are left untouched, and whether updating status recalculates the overall compliance score.

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 one-line purpose and scope, followed by a short behavioral note and a compact args list; nothing is wasted. Minor redundancy: '(optional)' repeats the schema's default=null, and 'Works across all frameworks' is more reassurance than actionable detail.

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?

For a mutation tool with no annotations and no output schema, the definition covers inputs well but says nothing about the response (updated control object? new score?) or failure modes, leaving the agent without expectations after invocation. It is adequate but has clear gaps for a write operation.

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 description coverage is 0%, so the description must compensate, and it largely does: it explains that control_id is a UUID obtainable from list_compliance_controls, and enumerates the four legal status values that appear nowhere in the schema (which declares status as a bare string with no enum). It leaves evidence_url's format/validation and the exact semantics of notes slightly under-specified.

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 ('Update the status, notes or evidence URL of a compliance control') and enumerates exactly which fields are mutable, so the agent knows the scope precisely. It does not explicitly differentiate itself from other update_* siblings, but it names list_compliance_controls as the source of control_id, which anchors it in the compliance workflow.

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 implied through the reference 'control_id ... (from list_compliance_controls)', giving a workflow hint of list-then-update. It does not state when to use this versus other update tools, nor any exclusions or prerequisites (e.g., required permissions, whether the control must already exist).

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