Skip to main content
Glama

accept_contract_draft

Idempotent

Records explicit caller acceptance of a reviewed contract draft's exact preview digest; unanswered questions block acceptance, and it never buys, imports, or certifies source truth.

Instructions

EXPLICIT CALLER ACCEPTANCE of the exact preview/requirements/assumptions digest after semantic review. Questions block acceptance. This never buys, imports or certifies source truth.

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": {
      "draftId": "<draftId>",
      "reviewDigest": "<reviewDigest>",
      "confirmAcceptance": "<confirmAcceptance>"
    },
    "name": "accept_contract_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes
reviewDigestYes
confirmAcceptanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare mutating, idempotent, non-destructive, closed-world behavior. The description adds genuine scope context beyond that: acceptance never 'buys, imports or certifies source truth', which bounds what the mutation means. It omits failure behavior when the digest does not match or when questions remain open.

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?

Three short sentences with the core action front-loaded and no filler. The all-caps emphasis and dense jargon ('semantic review', 'source truth') cost a little readability but every clause carries information.

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 3-param mutation tool with rich annotations and no output schema, the description covers preconditions and negative scope adequately. What remains unsaid is post-acceptance effect (e.g., whether export becomes available) and error semantics for a stale digest.

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 0%, so the description must compensate. It adds real meaning for reviewDigest (it must be the 'exact' digest that was reviewed) but says nothing about draftId or the confirmAcceptance const-true flag, leaving two of three parameters to be inferred from names.

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+resource: 'EXPLICIT CALLER ACCEPTANCE of the exact preview/requirements/assumptions digest'. This clearly distinguishes it from prepare/review siblings by naming the acceptance act and the artifact it targets, though it does not explicitly name an alternative tool.

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?

'after semantic review' and 'Questions block acceptance' give a concrete precondition for when to call it. It does not name a sibling alternative or state explicit when-not conditions, so it falls 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.