Skip to main content
Glama

Set security compliance framework

set_security_compliance_framework
Destructive

Enable or disable a compliance framework for the organisation (security.manage). Enabling starts scoring and monthly recording; disabling stops the record and hides the report. Reversible, but a disabled month is not recorded and cannot be recovered later.

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": {
      "framework_key": "<framework_key>",
      "enabled": "<enabled>"
    },
    "name": "set_security_compliance_framework"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue to enable, false to disable.
framework_keyYesFramework key: gdpr, iso27001, soc2, nist_csf or hipaa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses real behavioral consequences: enabling starts scoring and monthly recording, disabling hides the report, and a disabled month is permanently unrecorded. That is meaningful extra context for a destructiveHint=true tool, though the consequence of re-enabling and the response shape are left implicit.

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 tightly packed sentences with no filler: the operation and permission come first, the consequences and the irreversibility caveat follow. Every clause carries load.

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?

For a two-parameter mutation with no output schema, the definition covers the action, the permission, the side effects, and the irreversibility of lost months. What remains unaddressed is the response/confirmation behavior and what happens if the framework is already in the requested state.

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?

With 100% schema coverage, both parameters are already documented including the framework key values. The description adds the effect of the enabled flag (scoring and monthly recording starts or stops), which gives the boolean semantic weight beyond the schema's terse 'true to enable'.

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?

The description states a specific verb pair (enable/disable), the exact resource (compliance framework), and the scope (the organisation), plus the required permission (security.manage). This is clearly distinguishable from the read-oriented siblings such as list_security_compliance_frameworks or get_security_compliance_framework_report.

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 by the paired enable/disable semantics and the permission note, so an agent can infer when to reach for it. However, it never explicitly routes the agent to alternatives (e.g. listing frameworks or reading a report) or states preconditions such as the framework needing to exist first.

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.