Skip to main content
Glama

file_dissent

File or update a structured dissent on a draft contract, creating a new version with a tripwire trigger. Records concerns and predicted failures for audit and re-consent.

Instructions

File or update a structured dissent on a draft contract, creating a new version. Tripwires are data only. An agent files as its authenticated identity; an orchestrator may file for any participant. A dissent needs a tripwire before freeze or explicit excusal with a reason. Frozen contracts require amend_contract and consent.

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": {
      "contract_id": "<contract_id>",
      "dissent": "<dissent>"
    },
    "name": "file_dissent"
  }
}

Input Schema

NameRequiredDescriptionDefault
dissentYesStructured concern. Omit tripwire only for a draft. With excuse_reason, pass just {id}. by is bound to an authenticated agent; orchestrators specify a participant.
agent_tokenNoAuthenticate as an agent instead of an orchestrator.
contract_idYesThe contract id (ctr-<6 characters>-<n>) from propose_contract.
execution_idNoWith agent_token: the agent's execution.
orchestratorNoYour name as this contract's orchestrator (e.g. main). Only the orchestrator that proposed a contract can amend or freeze it.
excuse_reasonNoOrchestrator only: explicitly excuse this dissent by id. Its concern and this reason remain in version history and the audit log. Creates a new draft requiring re-consent.
resolve_objectionNoThe objector explicitly consents to the new version with how: dissented, retaining this dissent. Other participants must re-consent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations it discloses that a call creates a new contract version, that tripwires are inert 'data only' rather than executable hooks, and that identity is bound to an authenticated agent while orchestrators may act for participants. It stops short of describing rate limits, audit-log side effects for normal filings, or why the operation is non-idempotent, but the mutation and auth profile is well covered.

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?

Four compact sentences with the mutation and version effect front-loaded, followed by preconditions and the alternative tool. 'Tripwires are data only' is very terse and slightly cryptic out of context, keeping it from a perfect score, but no sentence is filler.

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?

For a seven-parameter tool with a nested dissent object and no output schema, the description covers the essentials an agent needs: identity model, version creation, the tripwire precondition, and the frozen-contract escape hatch. Return behavior and the interaction between 'resolve_objection' and re-consent are left entirely to schema text.

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 would be 3, but the description adds real meaning: the tripwire requirement explains when the 'tripwire' field may be omitted, the identity sentence clarifies 'by', 'agent_token' and 'orchestrator', and the excusal sentence clarifies 'excuse_reason' taking just an id. The remaining nested fields are left to 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?

The first sentence states a concrete verb and resource ('File or update a structured dissent') plus the key side effect ('creating a new version'), which is exactly what an agent needs to distinguish this mutation from a read of dissent state. The closing sentence further separates it from amend_contract by naming the frozen-contract condition.

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 a clear precondition ('A dissent needs a tripwire before freeze or explicit excusal with a reason') and names the alternative path for frozen contracts ('Frozen contracts require amend_contract and consent'). What it does not spell out is when to call this versus re-scoring or withdrawing an existing dissent, so guidance is strong but not exhaustive.

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