Skip to main content
Glama

get_contract_template

Read-onlyIdempotent

Inspect a free local CSV contract preset to view exact headers, validation rules, canonical contract, proposal details, synthetic samples, and limitations before preparing or reviewing a draft.

Instructions

FREE local explicit preset: exact headers/rules, canonical contract, proposal, synthetic pass/findings samples and limitations. Inspect its rules. Selecting it does not accept a draft or buy a report. Reuse prepare/review/accept for that workflow; confirmPurchase remains separate.

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": {
      "templateId": "<templateId>"
    },
    "name": "get_contract_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYes

Output Schema

NameRequiredDescriptionDefault
titleYes
headersYes
acceptedYes
examplesYes
proposalYes
templateIdYes
descriptionYes
limitationsYes
contractJsonYes
requirementsYes
templateVersionYes
importAuthorizedYes
purchaseAuthorizedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered; the description usefully adds that the preset is free, local, and has no accept/purchase side effects. Beyond that it does not say whether the returned rules are authoritative or how the synthetic samples relate to real validation output. Its value over the annotations is real but modest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the resource, which is good, but the opening is a run-on noun pile ("exact headers/rules, canonical contract, proposal, synthetic pass/findings samples and limitations") that is hard to parse, and the trailing "confirmPurchase remains separate" references a tool name outside the sibling set without context.

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?

An output schema exists, so return shape need not be described, and the side-effect and cost boundaries are well covered. What is missing is anything about the templateId argument or what the presets contain, which is the main thing an agent must decide before calling this one-parameter tool.

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 coverage is 0% and the single parameter templateId is undocumented in the description; the description never says that templateId selects among the enumerated presets (inventory_v1, customer_import_v1, scraper_export_v1) nor what those presets mean or how to choose between them. The enum values alone give no basis for choosing.

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 what the tool fetches: a free, locally-defined preset containing exact headers/rules, a canonical contract, a proposal, synthetic pass/findings samples and stated limitations, and it names the sibling workflows (prepare/review/accept) it is not. The verb is only implied by "get" and the head noun "preset" is buried under a dense noun pile, but the resource returned is identifiable.

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?

Explicitly bounds use: selecting the template does not accept a draft or purchase a report, and the prepare/review/accept workflow must be used for that. That is a clear when-not plus a pointer to alternatives, though it never states the obvious when-to-use (fetch the preset to inspect its rules before preparing a draft).

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