Skip to main content
Glama

prepare_contract_draft

Idempotent

Prepare a bounded generation request from CSV contract requirements and literal headers so your agent model can draft a proposal for separate review and submission.

Instructions

FREE LOCAL PREPARATION ONLY, not model generation. Return a bounded generationRequest for YOUR agent model using requirements and literal headers. Then submit its actual proposal with review_contract_draft. No purchase or automatic acceptance.

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": {
      "operationId": "<operationId>",
      "headers": "<headers>",
      "requirements": "<requirements>"
    },
    "name": "prepare_contract_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
headersYes
operationIdYes
requirementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, idempotent, non-destructive, closed-world), the description discloses that the call is free and local, performs no model generation, and triggers no purchase or acceptance. That is meaningful added context about side effects. It stops short of saying whether the returned request is persisted or how long it stays valid.

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 tight sentences with the key constraint ('FREE LOCAL PREPARATION ONLY, not model generation') front-loaded, followed by the action and the next step. The capitalization is emphatic but not wasteful; nothing is repeated.

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?

There is no output schema, so the description bears responsibility for describing the returned generationRequest, and it only characterizes it as 'bounded' without saying what fields it carries or how the agent should consume it. Combined with the unexplained operationId, an agent can call it but may not know what to do with the result.

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%, so the description must carry parameter meaning, and it only partially does: it notes that headers are passed literally and that requirements feed the request. The required operationId is never mentioned, and constraints such as the 12-header cap or the operationId pattern are left entirely to the schema.

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 names a specific action and output: it returns a bounded generationRequest built from requirements and literal headers, explicitly not performing model generation itself. This separates it from the sibling review_contract_draft, which receives the actual proposal. The term 'generationRequest' is an internal artifact not otherwise defined, which keeps it from a 5.

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?

It gives a clear workflow: prepare here, then submit the model's proposal via review_contract_draft, and states that no purchase or automatic acceptance occurs. It does not say when to prefer a template-based sibling such as get_contract_template or list_contract_templates, so exclusions are incomplete.

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