Skip to main content
Glama

resolve_violation

Mark a protocol violation as resolved by recording a resolution note, keeping swarm behavioral governance records accurate during autonomous coding sessions.

Instructions

Mark a protocol violation as resolved with a resolution note.

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>",
      "violationId": "<violationId>",
      "resolution": "<resolution>"
    },
    "name": "resolve_violation"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path to the project directory
resolutionYesDescription of how the violation was resolved
violationIdYesID of the violation to resolve

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 behavioral burden for a mutation tool. It does not say whether resolution is permanent or reversible, whether it affects protocol approval state or worker orchestration, whether a 'resolved' violation still appears via get_violations, or what happens on failure.

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 front-loaded sentence with no filler or redundancy; the action and its outcome appear together. It is appropriately sized, though so terse that it leaves little room for the missing behavioral detail.

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?

For an unannotated state-changing tool with no output schema, the description should at least say what the resolved state means downstream and whether the change is reversible. With zero annotation coverage, the single sentence is not enough to let an agent call it confidently in edge cases.

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%, so all three parameters (projectDir, violationId, resolution) are already documented inline. The description only alludes to the resolution field via 'with a resolution note' and adds no format, length, or ID-lookup guidance beyond the schema, making 3 the appropriate baseline.

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?

The description gives a specific verb ('mark') plus resource ('protocol violation') and the resulting state ('resolved'), so an agent can tell this is a mutation as opposed to the read-side sibling get_violations. It never names that alternative explicitly, so differentiation is inferred from verb semantics rather than stated.

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?

There is no guidance on when to use this versus get_violations or approve_protocol, no stated prerequisites (must the violation exist, must the protocol be in a particular phase), and no exclusions. Usage is only implied by the verb 'resolve'.

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