Workeey Quote Links

Cancel a Quote Link

cancel_quote_link

DestructiveIdempotent

Cancel a Quote Link so the customer can no longer approve it: the customer link then says the quote was cancelled. Call it only when the user clearly asks to cancel or withdraw the quote. To change prices or options instead, use revise_quote_link. There is no tool to undo a cancel. The answers and versions so far are kept. Needs the quote's manage_token (the code after # in the private link https://www.workeey.com/q/m/#…; the whole private link is accepted too).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cancel_quote_link"
  }
}

Input Schema

Name	Required	Description	Default
`manage_token`	No	The quote's private manage token: the long code after # in the private link (https://www.workeey.com/q/m/#<token>), returned as manage_token by create_quote_link. The whole private link is accepted too. Required, unless your MCP client already sends it as an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds what those hints cannot: the customer-facing link displays a cancelled state, the action is irreversible ('There is no tool to undo a cancel'), and existing answers and versions are retained. The remaining gap is only the response shape, which is minor given the effect is already described.

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?

Front-loads the effect before guidance, then caveats, then the parameter note — a sensible order with little waste. The token sentence duplicates the schema description and could be trimmed without information loss.

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

Completeness5/5

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

For a single-parameter mutation with no output schema, the description covers effect, irreversibility, data retention, usage gating, and the credential needed. Nothing an agent requires to call it correctly is missing.

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 100% and the schema already explains the manage_token format, the private-link URL pattern, and the Authorization: Bearer fallback. The description largely restates that, so it adds no meaning beyond the schema; baseline 3 applies.

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 and resource ('Cancel a Quote Link') plus the concrete outcome ('the customer can no longer approve it'). It also names the sibling it is not (revise_quote_link), so the agent can distinguish intent without opening 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 Guidelines5/5

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

Explicitly gates usage ('Call it only when the user clearly asks to cancel or withdraw the quote') and routes the alternative case to revise_quote_link for price/option changes. Both the when and the when-not are stated.

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

All Workeey Quote Links 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?