Skip to main content
Glama

get_compliance_report

Read-onlyIdempotent

Retrieve compliance reports for injection sessions: get session-specific followed, violated, and pending counts and compliance rates, or an agent-filtered aggregate summary of recent sessions.

Instructions

Get a compliance report for injection sessions: with inject_session_id, followed/violated/pending counts plus compliance_rate for that session; without it, an aggregate summary (total_sessions, overall_rate, must_rate, recent_sessions) filtered by optional agent_id and limit (default 10). compliance_rate/overall_rate/must_rate are null when no real MUST verdict exists yet (all pending/unknown); null never means 100%. Use report_compliance to record follow/violation status — this tool only reads it.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of recent sessions in the aggregate summary (default: 10)
api_keyNoAPI key for agent authentication (required if agent has a registered key)
agent_idNoFilter aggregate summary by agent
inject_session_idNoGet report for a specific injection session

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.11
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "API key for agent authentication (required if agent has a registered key)",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of recent sessions in the aggregate summary (default: 10)"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds valuable semantics the annotations cannot express: null rates mean no real MUST verdict exists yet and null never means 100%, which prevents a serious misinterpretation. It stops short of describing ordering or how recent_sessions is scoped beyond the limit default.

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 dense but front-loaded with the two-mode behavior, and each clause carries distinct information (mode selection, null semantics, sibling routing). The single-sentence structure is slightly long but no sentence is wasted.

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

Completeness5/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 compensates by naming the returned fields for both modes and explaining their edge-case values. An agent knows enough to call it correctly and interpret the result.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema: limit governs only the aggregate's recent_sessions list and agent_id filters only the aggregate, not the single-session branch. That scoping of parameter effect is genuinely beyond what the schema declares.

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 and resource and enumerates the two output modes (per-session counts vs aggregate summary) with the exact fields returned. It also names the sibling report_compliance as the write counterpart, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use rule: pass inject_session_id for a single-session report, omit it for an aggregate filtered by agent_id/limit. It also states an exclusion, directing writes to report_compliance, leaving nothing to inference.

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