Skip to main content
Glama

create_invoice_draft

Idempotent

Create a invoice 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_invoice_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
snapshotYes
enquiryIdNo
savedServicesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new context: the leads:read scope requirement and the retry pattern of reusing the same document ID and details. It does not say what happens to the draft afterwards or how review/approval works, which keeps it short of a 5.

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?

Four tight sentences, each covering a distinct concern (purpose, lead linking plus permission, service copying, pricing units, retry). Nothing is repeated and the core purpose is front-loaded.

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 deeply nested snapshot schema, no output schema and zero schema descriptions, the description covers the top-level parameters and the auth requirement but omits the shape and constraints of the snapshot payload. An agent would still need to read the schema carefully to construct a valid call.

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 carries the burden, and it does explain enquiryId, savedServices, the minor-units convention for unitAmount, and reuse of the id on retry. It says nothing about the snapshot object's required seller/customer/items/dueDate/notes structure or the optional discount, schedule, agreement and depositPercent fields, leaving most of the nested schema 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 invoice draft for review') and names the product, so the agent knows exactly what is produced. It does not explicitly distinguish the tool from the sibling create_invoice_from_quote, leaving that contrast to inference.

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?

It gives conditional guidance for individual inputs (pass an enquiry ID to link a lead, use savedServices to copy service details, supply unitAmount when a service has no fixed price) and a retry instruction. However, it never states when to choose this tool over create_invoice_from_quote or create_quote_draft, so the alternative-selection guidance is only implied.

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