Skip to main content
Glama

freeze_contract

Freeze a contract for execution only when every participant agrees to its current version; the orchestrator can excuse unresolved objections with audited reasons.

Instructions

Freeze a contract so it can be executed. Only its orchestrator can, and only once every participant has agreed to its current version. Refuses, listing every reason, while an objection or UNCLEAR answer is unresolved, a participant has not answered about the current version, a consent round is in flight (abandon_round declares a dead one abandoned), the source session is busy, or, for a child contract, while the parent is not frozen or the caller is neither the parent task's persona nor the parent's orchestrator. excuse sets objections aside, each with a reason; excusals and the frozen sha256 go to the audit log. Freezing starts nothing: the run starts with execute, when the human asks.

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>",
      "orchestrator": "<orchestrator>"
    },
    "name": "freeze_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
excuseNoObjections (or missing answers) to set aside: [{agent, reason}]. Each is recorded and audited.
contract_idYesThe contract id (ctr-<6 characters>-<n>) from propose_contract.
orchestratorYesYour name as this contract's orchestrator (e.g. main). Only the orchestrator that proposed a contract can amend or freeze it.
abandon_roundNoDefault false. True: declare an unfinished consent round abandoned (its process died or hangs): its missing answers are recorded as unclear, which still need excusing, and the abandonment is audited.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses authorization requirements, the complete set of refusal reasons including the parent-frozen rule for child contracts, that refusals list every reason, and that excusals plus the frozen sha256 land in the audit log. It does not describe the success response shape, but that gap is minor for a precondition-heavy mutation.

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?

Front-loads the purpose and the authority rule, and the long refusal sentence, while dense, carries only operative conditions. The final sentence about execute is well placed but the refusal clause is a run-on that could be broken up for faster scanning.

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 precondition-gated mutation with no output schema and no annotation detail, the description supplies authorization, gating conditions, failure modes, audit behavior, and where the follow-on action lives. An agent can decide to call it, predict refusals, and recover without further information.

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 real meaning: excuse is characterized as setting objections (or missing answers) aside that would otherwise block the freeze, and abandon_round is framed as declaring a dead round abandoned whose missing answers still need excusing - a coupling the schema hints at but does not spell out.

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?

Opens with a specific verb and resource: 'Freeze a contract so it can be executed.' It immediately bounds what freezing is not ('Freezing starts nothing: the run starts with execute'), which distinguishes it cleanly from the execute sibling.

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?

Gives explicit preconditions (only the orchestrator; only when every participant has agreed to the current version) plus a full when-not list of refusal conditions. It also names concrete escape hatches - abandon_round for a dead consent round, excuse for objections - so an agent knows which path to take instead of just being blocked.

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