Skip to main content
Glama

review_contract_draft

Idempotent

Validates a proposed CSV contract JSON against the public profile and exact headers, then stores a pending preview for review without accepting or repairing it.

Instructions

Review YOUR model proposal JSON against the public contract profile and exact headers; store a pending preview. Does not accept it, generate with a server model, buy a report or repair data. Rejected proposals stay rejected; do not silently weaken requirements.

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": {
      "draftId": "<draftId>",
      "proposalJson": "<proposalJson>"
    },
    "name": "review_contract_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes
proposalJsonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is partly covered. The description adds real value by disclosing the side effect (stores a pending preview) and the non-repair, non-acceptance semantics. It does not explain what the preview contains or what happens on rejection beyond 'stays rejected'.

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 core action and followed by exclusions. Every clause carries information, though the capitalized 'YOUR' and the 'buy a report' clause are slightly odd in tone.

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?

No output schema exists, so the description should say more about the returned preview, and it does not. For a tool with a side effect and two required parameters, the definition covers intent and boundaries but leaves the draftId semantics and result shape unexplained.

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 largely does not. proposalJson is implied by 'model proposal JSON', but draftId (a 32-hex identifier) is never explained, nor is the expected JSON shape or header format. This leaves a meaningful gap for a 2-parameter tool.

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: reviewing a model proposal JSON against the public contract profile and exact headers, then storing a pending preview. It also distinguishes itself from accept_contract_draft by explicitly saying it does not accept the draft. Slightly dense phrasing ('YOUR model proposal JSON') 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?

Gives clear negative guidance: it does not accept, does not generate with a server model, does not buy a report, and does not repair data, which routes the agent away from siblings like accept_contract_draft and start_validation. It also states that rejected proposals stay rejected and requirements must not be silently weakened. It lacks an explicit positive 'use this when' trigger, so not a 5.

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