Skip to main content
Glama

Get security compliance framework report

get_security_compliance_framework_report
Read-only

One compliance framework's report: control by control what the platform evidence shows (scanner coverage, findings under review, dispositions, audit trail, access grants), the score, and the month's trend. Live when month is omitted; a recorded month (YYYY-MM) returns what was captured then, so an auditor's question about last quarter is answered from the record. Read-only. The framework must be enabled (list_security_compliance_frameworks).

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>"
    },
    "name": "get_security_compliance_framework_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoRecorded month as YYYY-MM. Omit for the live report.
framework_keyYesFramework key: gdpr, iso27001, soc2, nist_csf or hipaa.

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?

The readOnlyHint annotation already covers safety, and 'Read-only' merely restates it. Beyond that, the description adds real behavioral context: the framework-enabled prerequisite and the crucial snapshot semantics that a recorded date returns what was captured at the time rather than recomputed data. It doesn't reveal response size, pagination, or a partial-report case when a framework was disabled for part of the window.

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?

A single dense block with the payload description front-loaded and the live/recorded distinction following immediately. Almost every clause earns its place, though 'Read-only' duplicates the readOnlyHint annotation and could be dropped without loss.

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 only two well-documented parameters and no output schema, the description carries the right burden by enumerating what the report contains and how the time window behaves. The prerequisite pointer to the frameworks-list tool closes the main gap an agent would hit at call time. Minor omissions remain around volume/shape of the returned evidence.

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?

Schema coverage is 100% — the schema already documents both month (omit for live) and framework_key with its accepted values — so the baseline is 3. The description reinforces the recorded-vs-live distinction with an audit use case, but adds no new format, default, or constraint information beyond the schema.

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 — one compliance framework's report, control by control, with score and month trend — and the singular 'one framework's' framing separates it from cross-framework siblings like get_security_compliance_overview. The enumerated evidence types (scanner coverage, findings under review, dispositions, audit trail, access grants) make the payload concrete rather than generic.

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?

It gives clear selection logic between the two modes: omit month for the live view, supply YYYY-MM for a point-in-time record, with the auditor/last-quarter case spelled out. It also names the prerequisite that the framework must be enabled and points at list_security_compliance_frameworks to obtain keys. It stops short of routing to get_security_compliance_overview when the agent actually needs a cross-framework roll-up.

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.