Skip to main content
Glama

apply_quote_agreement_template

Copy a saved agreement template into a draft quote using its current revision.

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": {
      "quoteId": "<quoteId>",
      "templateId": "<templateId>",
      "revision": "<revision>"
    },
    "name": "apply_quote_agreement_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYes
revisionYes
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful constraint that content lands in a draft quote and uses the template's current revision, but it does not address the non-idempotent hint (repeated calls may duplicate copied content) or what happens to existing quote content, which is the most consequential behavior for an agent to know.

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?

One front-loaded sentence with no filler, which is structurally clean. For a mutation tool with three undocumented required parameters it is under-specified rather than appropriately concise, so the brevity costs more than it saves.

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?

With zero schema description coverage, no output schema, and non-idempotent mutation semantics, the description should explain the target-state requirement, replacement behavior, and result. None of that is present, leaving meaningful gaps for an agent invoking it on a real quote.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 all meaning, and it does partially: it maps the three parameters to a source template, a target draft quote, and the template's revision. However, "using its current revision" is ambiguous against a required integer revision argument, and it adds nothing about valid template/revision combinations or the quote's expected state.

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 uses a specific verb and resource pair ("Copy a saved agreement template into a draft quote"), so an agent knows exactly what operation is performed and on what objects. It does not explicitly contrast itself with siblings like save_contract_template or create_quote_draft, so it stops 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?

There is no when-to-use guidance, no alternatives named, and no prerequisites stated beyond the implicit hint that the target must be a draft quote. An agent is left to infer whether the template must be saved first, whether an existing agreement in the quote is replaced, and when to prefer this over other quote-creation tools.

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