Skip to main content
Glama

prepare_contract_review

Read-onlyIdempotent

Check an unsigned contract draft against the content hash returned by get_contract and identify it for owner review in Cockatoo.

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

Input Schema

NameRequiredDescriptionDefault
idYes
contentHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations fully declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds the unsigned-draft precondition and the Cockatoo-side outcome, but leaves the meaning of 'identify it for owner review' opaque enough to be read as either a mere verification result or an actual flag being created, which sits uneasily with readOnlyHint. It also says nothing about behavior when the hash does not match, the single most important behavioral question for a check tool.

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?

A single front-loaded sentence with no filler, leading with the action before the side effect. It could be slightly sharper by naming which value comes from where rather than embedding it in the clause.

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?

With only two required parameters and a rich annotation set, the definition is nearly sufficient, but there is no output schema and the description does not say what the tool returns or what it returns when verification fails. For a verification tool, the mismatch outcome is core information an agent needs before deciding to call it.

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 carry parameter meaning; it partially does by stating that contentHash is the value returned by get_contract, establishing provenance the schema only expresses as a 64-hex pattern. The id parameter is not explained at all, and neither parameter is named explicitly, so the compensation is incomplete rather than absent.

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 pairs a specific verb ('Check ... against the content hash') with a specific resource (an unsigned contract draft) and adds the downstream effect ('identify it for owner review in Cockatoo'). It is clearly distinct from get_contract, which only retrieves, and from the create/update draft siblings. It stops short of naming a sibling it is explicitly not, so a 4 rather than 5.

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?

Use is implied rather than stated: the contract must be unsigned and the agent must already hold a content hash from get_contract, which establishes a call ordering with get_contract. There is no explicit when-not guidance, no statement of what to do on hash mismatch, and no routing guidance against siblings such as prepare_sales_document_review or update_contract_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