Skip to main content
Glama

report_compliance

Idempotent

Marks memories injected in a previous session as followed, violated, or unknown with optional evidence, then returns updated/total counts so agents can verify compliance reports were stored.

Instructions

Report compliance for a previous injection session returned by session_start. Call this to mark which injected memories were followed or violated, with optional evidence. Reports are processed item by item: a bad item is logged and skipped while the call still succeeds, so the response's updated/total counts must be checked rather than assuming all reports were stored. Requires a compliance-enabled server; no agent API key is required by this tool.

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": {
      "inject_session_id": "<inject_session_id>",
      "reports": "<reports>"
    },
    "name": "report_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoAPI key for agent authentication (required if agent has a registered key)
reportsYesList of compliance reports, one per memory
agent_idNoID of the agent reporting complianceunknown
inject_session_idYesThe inject_session_id from a previous session_start call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.11
    • addedInput schema / properties / agent_id
      Added value: +{
      +  "default": "unknown",
      +  "description": "ID of the agent reporting compliance",
      +  "type": "string"
      +}
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "API key for agent authentication (required if agent has a registered key)",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: reports are processed item by item, bad items are logged and skipped while the call still succeeds, and callers must check updated/total counts rather than assume all reports stored. It also notes the compliance-enabled server requirement and that no agent API key is required by this tool, which is valuable operational context for a non-readOnly call.

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?

The description is front-loaded with purpose and usage, then adds only operationally important caveats about partial success, server requirements, and authentication. Every sentence carries relevant information without redundancy.

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?

For a write-like tool with no output schema, the description covers the key risks an agent needs: partial-item failure behavior, the need to inspect updated/total counts, server enablement, and API-key irrelevance for this tool. Combined with annotations, it provides enough context to invoke and interpret the tool correctly.

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 schema already documents the parameters well. The description still adds useful meaning by tying inject_session_id to a previous session_start and explaining that reports mark injected memories as followed or violated with optional evidence, which goes beyond the raw field documentation.

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: reporting compliance for a previous injection session returned by session_start. It also clarifies the action as marking which injected memories were followed or violated, which distinguishes it from sibling tools like get_compliance_report.

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 clearly says to call this to mark followed or violated injected memories from a prior session_start, giving a concrete usage context. It does not explicitly state when not to use it or name get_compliance_report as the read-side alternative, so it stops short of full routing guidance.

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