Skip to main content
Glama

get_contract_draft

Read-onlyIdempotent

Reads the original local draft for a given operation under the configured buyer credential profile, returning the stored contract content without sending a model request or making a purchase.

Instructions

Read the original local draft operation under this configured buyer credential profile. No model request or purchase.

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

Input Schema

NameRequiredDescriptionDefault
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds useful beyond-annotation context: no model request and no purchase occur, and "original" implies the stored draft is returned unmodified. It still omits what happens when the operationId is unknown, and since no output schema exists, nothing is said about the return shape.

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 with no filler, and the core action is front-loaded. The phrasing "draft operation under this configured buyer credential profile" is dense and slightly jargony, but nothing is redundant.

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 single-parameter read tool with full annotation coverage, the definition is minimally adequate: it conveys that this is a free, local, non-mutating read. It falls short on how to obtain a valid operationId and on what the call returns, which matters because there is no output schema to carry that information.

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% for the single required operationId, and the description never names or explains it beyond the loose phrase "draft operation." The agent gets no guidance on the ID's format, source, or scope, leaving the only parameter effectively undocumented.

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 and resource ("Read the original local draft") tied to the contract-draft family, so the agent knows it retrieves an existing draft rather than creating or validating one. It does not explicitly distinguish itself from siblings such as review_contract_draft or get_contract_template, so it falls short of 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 Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives like accept_contract_draft or review_contract_draft. The only implicit signal is "No model request or purchase," which hints at a cheap read but does not tell the agent when to pick this tool over its siblings.

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