Skip to main content
Glama

create_quote_draft

Idempotent

Create a quote draft for review in Cockatoo. Pass an enquiry ID to link it and use its customer name and email; requires leads:read. Use savedServices to copy service details from this business. Supply unitAmount in minor units when a service has no fixed price. Reuse the same document ID and document details 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>",
      "snapshot": "<snapshot>"
    },
    "name": "create_quote_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
snapshotYes
enquiryIdNo
savedServicesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (write, non-destructive, idempotent), the description adds genuinely useful behavior: the leads:read scope requirement, that unitAmount is in minor units when a service has no fixed price, and that the same document ID and details should be reused on retry. That last point directly elaborates the idempotentHint in a way an agent can act on. It stops short of describing the draft's lifecycle after creation or any limits on concurrent drafts.

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?

Four compact sentences, front-loaded with the core action and followed by the operational constraints an agent needs. No filler or repetition. Density is high but each clause carries a distinct fact (linking, scope, price units, retry).

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 tool with a large nested input and no output schema, the description covers linking, permissions, pricing units, and retry safely. It leaves the snapshot payload — the largest and most error-prone part of the contract — entirely unexplained, so an agent still cannot construct a valid call from the description alone.

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 parameter meaning. It does explain enquiryId (links the quote and supplies customer name/email), savedServices (copies service details), and the minor-units convention for unitAmount — all valuable. However, the bulk of the schema is the deeply nested snapshot object (items, taxRate, schedule, agreement, discount, depositPercent), which the description never touches, leaving most parameters 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?

The description opens with a specific verb and resource: 'Create a quote draft for review in Cockatoo.' That tells an agent exactly what is produced (a draft, not a finalized quote). It does not distinguish this tool from siblings like create_invoice_from_quote or create_contract_draft, so the agent must rely on the name alone to pick between them.

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?

Usage is implied rather than stated: the draft is 'for review', an enquiry ID can link it, and savedServices copies details from the business. There is no explicit statement of when to choose this over create_invoice_from_quote or create_contract_draft, and no exclusions or prerequisites beyond the leads:read scope.

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