Skip to main content
Glama

List security compliance frameworks

list_security_compliance_frameworks
Read-only

List the curated compliance frameworks (GDPR, ISO 27001, SOC 2, NIST CSF) with whether each is enabled for the organisation and, when enabled, its live score: the controls Ankra maps to platform evidence and how many currently pass. Read-only. Use it for the framework_key get_security_compliance_framework_report and set_security_compliance_framework take.

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_security_compliance_frameworks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description restates 'Read-only', which is redundant but harmless. Beyond that it discloses real behavioral detail the annotations don't: results are organisation-scoped, disabled frameworks score nothing, and enabled ones report mapped-control counts that currently pass. No output schema exists, so this return-shape disclosure carries genuine weight.

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?

It is front-loaded with the action and resource, then layers return detail and the routing hint. The colon-chained clause about 'controls Ankra maps to platform evidence' is dense, and 'Read-only' duplicates the annotation, but no sentence is filler.

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 zero parameters, no output schema, and trivial annotations, the description does the heavy lifting well: it names the returned fields (enabled flag, live score, mapped control counts) and the downstream consumers. Minor gaps remain on ordering/pagination and how the score is computed, but nothing needed to call it correctly is missing.

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

Parameters3/5

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

The tool takes zero parameters, so the baseline is 4, but the description spends its parameter budget on the framework_key concept indirectly rather than any input semantics. There is nothing to document, and nothing misleading is said — adequate but no added parameter meaning is possible.

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 pairs a specific verb ('List') with a precise resource and enumerates the contents (GDPR, ISO 27001, SOC 2, NIST CSF) plus per-framework fields: enabled status and live score with controlling counts. It also names the two sibling tools the output feeds, so an agent can separate this discovery call from get_security_compliance_framework_report and set_security_compliance_framework without opening schemas.

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?

'Use it for the framework_key get_security_compliance_framework_report and set_security_compliance_framework take' explicitly states the routing purpose: call this first to obtain keys for the two downstream tools. It lacks an explicit when-not clause (e.g. versus get_security_compliance_overview), but the sequencing guidance is unambiguous.

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.