QuoteBuild

Prepare variation send

prepare_variation_send

Previews the exact current variation recipient and payload, then stores a one-use ten-minute confirmation token. This does not send.

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": {
      "variationId": "<variationId>",
      "expectedVersion": "<expectedVersion>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "prepare_variation_send"
  }
}

Input Schema

Name	Required	Description	Default
`variationId`	Yes
`idempotencyKey`	Yes
`expectedVersion`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`warnings`	Yes
`provenance`	No
`assumptions`	Yes
`nextActions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only say this is non-destructive and not read-only; the description adds the behavior that matters — content is snapshotted as 'exact current', the token is single-use and expires in ten minutes, and nothing is transmitted. It does not say what the token binds to (payload, recipient, version) or what happens to a previously issued token on a repeat call, which are the remaining behavioral unknowns.

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?

A single front-loaded sentence carries the action and its artifact, and the short 'This does not send' lands the most important constraint last. No filler, no restatement of the tool name.

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?

With annotations and an output schema present, the safety profile and return shape are covered elsewhere, and the ten-minute window is stated. What is missing is the connective tissue of the two-phase flow: where the token is surfaced and how it is redeemed, plus any guidance on invalidating or retrying, which an agent needs to complete the send successfully.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so all three parameters rely on the description, which never mentions any of them by name. 'Exact current' hints faintly at expectedVersion being a freshness/concurrency check, but idempotencyKey and expectedVersion semantics — format, what a mismatch returns, whether retries with the same key reuse the token — are left entirely undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (previews) and resource (the current variation recipient and payload), plus the side effect it produces (a one-use ten-minute confirmation token). The closing 'This does not send' separates it cleanly from send_variation, so an agent can distinguish the two without inspecting either schema.

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?

The two-step framing (preview, then hold a token) and the explicit 'This does not send' tell the agent this is the pre-send step rather than the send itself. It stops short of naming send_variation as the follow-up or stating what conditions require re-running it, so it is clear context without a full when/when-not map.

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

All QuoteBuild 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?