Skip to main content
Glama

get_violations

Retrieve protocol violations recorded during enforcement and filter them by severity, resolution status, worker, feature, or protocol to diagnose governance issues.

Instructions

Get protocol violations with optional filtering. Shows violations recorded during enforcement.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "get_violations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum violations to return (default: 20)
formatNoOutput format (default: pretty)
offsetNoSkip first N violations (default: 0)
resolvedNoFilter by resolved status (true/false, omit for all)
severityNoFilter by severity
workerIdNoFilter by worker ID
featureIdNoFilter by feature ID
projectDirYesAbsolute path to the project directory
protocolIdNoFilter by protocol ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does not say the tool is read-only, how results are ordered, whether a total count is returned alongside the page, or whether resolved and unresolved violations are interleaved by default — all material for a 9-parameter query tool.

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?

Two short sentences, front-loaded with the verb and resource. The second sentence ("Shows violations recorded during enforcement") is largely redundant with the first and could have been spent on ordering or pagination instead.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters, no annotations, and no output schema, the definition should explain the shape of a returned violation and how the filter set behaves. Instead it leaves resolution semantics, ordering, and pagination behavior entirely to the schema, which only documents individual fields in isolation.

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 description coverage is 100%, with defaults, enums, and bounds documented inline for every parameter, so the baseline is 3. The description adds nothing beyond "optional filtering" — no guidance on how severity, resolved, workerId, and protocolId filters combine or whether they are ANDed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get protocol violations") plus the data's origin ("recorded during enforcement"), so the agent knows exactly what entity is being read. It does not differentiate itself from neighboring reads such as get_audit_log or get_review_results, so sibling disambiguation is left to inference.

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

Usage Guidelines2/5

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

The only usage signal is "with optional filtering," which restates the schema rather than telling the agent when to prefer this tool over get_audit_log, get_review_results, or get_worker_confidence. No when-not conditions, no prerequisites, no mention of what a violation represents in the workflow.

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