SalesHookAI

Save quote draft

saveQuoteDraft

Creates a new quote as a draft in the user's account, with positions, prices and optional customer and project data. The draft is never sent to anyone; the user reviews, edits and sends it in the app.

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": {
      "quoteData": "<quoteData>"
    },
    "name": "saveQuoteDraft"
  }
}

Input Schema

Name	Required	Description	Default
`quoteData`	Yes	Quote object: { positions: [{ description, quantity, unit, unitPrice, category? }], customerName?, customerCompany?, customerAddress?, customerEmail?, customerIsConsumer?, projectName?, projectDescription?, letterText?, vatRate?, validUntil? (YYYY-MM-DD) }. Units: Stk, h, m, m², m³, kg, Pauschale. A customer without company is treated as a consumer. Always saved with status "draft" — never sent automatically.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish write, non-destructive, non-idempotent behavior, so the description's added detail is the real value: the draft is never sent to anyone automatically and the send step happens in the app. That discloses a genuinely non-obvious side effect and a workflow boundary. It does not mention whether repeated calls create duplicates, which the non-idempotent hint implies.

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 sentences with zero filler; the creation action and the never-sent guarantee are both front-loaded. Every clause carries information an agent can act on.

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 single-parameter tool with fully documented nested schema and no output schema, the description covers the essential action and the key behavioral caveat. The only real omission is what comes back (e.g. a quote id) and how duplicate submissions are handled, which matters given idempotentHint=false.

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 100% and the nested quoteData schema already documents fields, units, date format, and the consumer rule. The description only glosses the parameter as 'positions, prices and optional customer and project data', adding no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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 names a specific verb and resource ('Creates a new quote as a draft') and pins down the scope with the contents it accepts (positions, prices, optional customer and project data). It is distinguishable from status-changing or link-generating siblings via the explicit 'draft' framing, though it never names an alternative tool directly.

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 only implied: an agent can infer this is the creation path for an unsent quote. The description does clarify the key downstream behavior (the user reviews, edits and sends it in the app), which hints at when this tool stops being the right choice, but it gives no explicit 'use this instead of updateQuoteStatus/generateQuoteLink' routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SalesHookAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?