Skip to main content
Glama

update_contract_draft

Replace the editable terms and customer details of a standalone draft contract. Supply its current content hash.

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": {
      "id": "<id>",
      "contentHash": "<contentHash>",
      "contract": "<contract>"
    },
    "name": "update_contract_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
contractYes
contentHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the description's main added value is the "Supply its current content hash" requirement, which reveals a stale-write guard. It does not disclose what happens on a hash mismatch, whether uneditable fields are preserved, or whether the draft must be in a particular state.

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 tight sentences, front-loaded with the action and followed by the hard prerequisite; nothing is padded. Brevity is appropriate, though it leaves ambiguity around "standalone" and the missing title field.

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 a destructive-in-spirit replace operation on a nested object with zero schema description coverage and no output schema, the description is thin. An agent still lacks the id's meaning, the source of the contentHash, the failure behavior on mismatch, and confirmation that title is also being replaced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema is a nested object with additionalProperties=false, so the description must carry the burden. It covers the gist of contract.terms and the customer fields plus contentHash, but says nothing about the required id (UUID of the draft), where the hash comes from, its 64-hex format, or the required contract.title field it never mentions.

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?

"Replace the editable terms and customer details of a standalone draft contract" gives a specific verb (replace) and a specific resource (draft contract fields), and the word "standalone" plus "draft" distinguishes it from create_contract_draft and update_sales_draft. It stops short of naming any sibling explicitly, so the differentiation is inferential 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 Guidelines3/5

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

Usage is only implied: the tool replaces content on an existing draft and requires its current hash, which signals optimistic-concurrency updating rather than creation. There is no explicit statement of when to prefer this over create_contract_draft or update_sales_draft, and no mention of preconditions such as the draft being unpublished or editable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources