Skip to main content
Glama

create_invoice_from_quote

Idempotent

Create a draft invoice from an accepted quote in the approved business. Any required deposit must already be paid. Reuse the same idempotency key 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": {
      "quoteId": "<quoteId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_invoice_from_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the safety profile is known; the description adds that the output is a DRAFT rather than a finalized invoice and that a deposit precondition applies, which is genuine added context. The idempotency retry note largely restates idempotentHint=true, and permissions or side effects are not described, so this is modest value beyond structured data.

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?

Three short sentences, each carrying distinct information: what is created, the precondition, and the retry rule. Nothing is redundant or buried.

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

Completeness4/5

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

For a two-parameter creation tool with no output schema, the description covers purpose, prerequisites, and retry behavior adequately. It does not say what identifier or object the caller receives back, which is a minor gap given the absence of an output schema.

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 coverage is 0%, so the description must carry parameter meaning; it implies quoteId ('from an accepted quote') and names idempotencyKey ('reuse the same idempotency key on retry'), which is useful. It does not convey the UUID format for quoteId or the 8-128 character pattern for the key, so compensation is only partial.

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 a draft invoice') plus the source it derives from ('from an accepted quote'), which lets an agent distinguish this from create_invoice_draft. It does not explicitly contrast itself with that sibling, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear preconditions: the quote must be accepted, the business approved, and any required deposit already paid. It lacks explicit when-not or alternative routing (e.g., when to use create_invoice_draft instead), so it is contextual rather than fully routing.

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