Skip to main content
Glama

save_contract_template

DestructiveIdempotent

Create or replace a reusable contract template. Use the same template ID on retry.

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

Input Schema

NameRequiredDescriptionDefault
idYes
bodyYes
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, and the description usefully adds that the operation replaces an existing template rather than only creating one, plus the retry contract. It stops short of the most important behavioral detail for a destructive write: that replacing an existing template overwrites its prior body irreversibly.

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

Conciseness5/5

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

Two short sentences with zero filler, and the core upsert behavior is front-loaded ahead of the retry note. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-read-only mutation with three undocumented required parameters and no output schema, the definition leaves too much unsaid. An agent knows it is an upsert and how to retry, but not what each parameter means or what existing data the replace will destroy.

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 carries the burden for all three required parameters. It only alludes to the id parameter (reuse on retry); name and body are never explained, nor is the fact that body is the template content subject to an 8000-character limit.

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 ("Create or replace a reusable contract template") and makes the upsert semantics explicit, which an agent cannot infer from the name alone. It does not explicitly distinguish itself from siblings like apply_quote_agreement_template or list_contract_templates, but the purpose is unambiguous.

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?

The retry instruction ("Use the same template ID on retry") is genuinely useful operational guidance for a write tool. However, there is no guidance on when to use this versus creating a draft or applying an existing template, and no stated prerequisites or permissions.

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