Skip to main content
Glama

create_contract_draft

Idempotent

Create an unsigned contract draft for review in Cockatoo. Reuse the same idempotency key on retry.

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": "<contract>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_contract_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
contractYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the created artifact is unsigned and that retries should reuse the key, but does not say what a duplicate key returns, whether a draft is visible to others, or what state the resource is left in. 'Reuse the same idempotency key' partially restates idempotentHint=true, though it converts it into actionable guidance.

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 short sentences, front-loaded with the core action and followed by the retry caveat. 'in Cockatoo' is mildly redundant given the server context, but nothing else is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create mutation with no output schema, the definition omits what is returned (e.g. a draft identifier needed to chain into update_contract_draft or prepare_contract_review) and what 'for review' implies about subsequent workflow steps. The rich input schema and annotations cover the mechanics, so the gap is meaningful but not fatal.

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% with two required parameters, one of them a nested contract object containing title, customer_name, customer_email and terms. The description clarifies the idempotencyKey's retry semantics, which is genuine added meaning, but says nothing about the nested contract fields or constraints such as the terms length limit.

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 states a specific verb and resource ('Create an unsigned contract draft') and adds scope with 'for review in Cockatoo' plus the 'unsigned' qualifier. It does not explicitly differentiate itself from siblings such as update_contract_draft or create_quote_draft, but the action and artifact are unambiguous.

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 implied: this is the tool for producing a new, not-yet-signed draft for review. The retry guidance ('reuse the same idempotency key on retry') is a useful operational cue, but there is no explicit statement of when not to use it, nor a named alternative for updating or finalizing an existing draft.

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