Skip to main content
Glama

Workeey Quote Links

Create a Quote Link (the customer approves online)

create_quote_link

Create a Quote Link: a web page where the user's customer sees a quote for a job, picks one of up to 4 options and any add-ons, types their name, and approves, declines or asks for changes. Free; nobody needs an account. For a tradesperson or small service business who wants to send a customer a quote or estimate they can approve online.

Call it ONLY when the user asks you to publish the quote for them: the page is live the moment it is created. Otherwise give the user a ready-made link, which publishes nothing (price_check's draft_link, or https://www.workeey.com/quote-links/new#draft= followed by the quote JSON passed through encodeURIComponent): they open it, check the quote and press Create approval link themselves.

Before calling: use only prices the user gave you, or a starting price from price_check, shown with its sources, that they agreed to (never invent or guess one; ask), and confirm the details with the user, because the page is live as soon as it is created (it can be revised or cancelled later).

Rules for every text field: no links or web addresses, no email addresses (only business.email), and no payment details (Zelle, Venmo, Cash App, PayPal, bank, card or account numbers, crypto); the user sends payment details to the customer themselves. customer.name is a display name only, such as "Dana": never the customer's phone, email or address.

Returns customer_url, manage_url and manage_token. Give the customer_url to the user to send to their customer. Give the manage_url to the user only, and tell them to save it: it works like a password (it shows the customer's answer and can revise or cancel the quote), so it never goes to the customer. Keep manage_token for get_quote_status, revise_quote_link and cancel_quote_link. If the call returns errors, each one names the field, the problem and the fix: apply every fix and call again.

Workeey adds up the totals; tax is applied only as supplied (a rate, an amount or a note). Workeey does not verify businesses or quotes. Quote Links is not the estimates feature inside the Workeey app. Full guide: https://www.workeey.com/quote-links/for-ai/

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "Replace 50-gallon gas water heater",
      "options": [
        {
          "name": "Standard",
          "items": [
            {
              "unit_price": 1600,
              "description": "50-gallon gas water heater, installed"
            }
          ]
        }
      ],
      "business": {
        "name": "Rivera Plumbing"
      },
      "customer": {
        "name": "Dana"
      }
    },
    "name": "create_quote_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxNoOptional. Tax exactly as the user supplies it: Workeey never decides tax rules. Send ONE of rate_percent (applied to the chosen option plus the chosen add-ons), amount (a fixed tax amount) or note (for example "Tax not included"). Leave tax out if the user gave no tax information.
notesNoOptional. Anything else the customer should know: what is included, timing, access. No links, email addresses or payment details (Zelle, Venmo, Cash App, PayPal, bank or card numbers, crypto).
termsNoOptional. The business's terms, such as warranty or cancellation. No links, email addresses or payment details (Zelle, Venmo, Cash App, PayPal, bank or card numbers, crypto).
titleYesThe job, in a few words.
addonsNoOptional. Extras the customer can tick on top of the option they pick (up to 10).
sourceNoOptional. Which AI app is making this quote. Recorded as an unverified claim and never shown to the customer.
depositNoOptional. Deposit wording shown on the quote: percent OR amount, and an optional note. Text only: Workeey takes no payments.
optionsYesThe choices the customer picks between: 1 to 4 options (for example Standard and Premium), each priced on its own. A quote with a single price has one option. Workeey adds up every option, so send no totals.
businessYesThe user's own business, the one sending the quote. The customer sees these details marked as provided by the creator, not verified by Workeey.
currencyNoOptional. Three-letter ISO 4217 code of a currency with cents (2 decimals), like USD, CAD or EUR. Default USD. A currency without 2-decimal cents (JPY, KWD) isn't supported yet.USD
customerYesWho the quote is for: a display name only. Never the customer's phone, email or address; quote links get shared and stay in chat history.
locationNoOptional. Where the job is: city and state only, never the customer's street address.
exclusionsNoOptional. What the price does not include.
valid_untilNoOptional. The date the quote is valid until, YYYY-MM-DD. Default 30 days from today; at most 365 days ahead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a non-readonly, open-world, non-idempotent but non-destructive write. The description adds substantial behavioral context beyond that: the page is live the moment it is created, it can be revised or cancelled later, nobody needs an account, text fields prohibit links/emails/payment details, and manage_url behaves like a password. It also explains that errors name the field, problem and fix, though it does not describe rate limits or any auth requirements, so a 5 is not warranted.

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?

The description is long but well organized and front-loaded: purpose and the publish-only condition come first, followed by pre-call checks, field rules, return handling and error behavior. Every major paragraph carries operational value for a high-stakes 14-parameter publish action. Some repetition of the no-links/no-payment rules across sections and the schema keeps it from being maximally concise.

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?

There is no output schema, so the description carries the burden of explaining returns, and it does: customer_url, manage_url and manage_token, including who each may be shared with and which follow-up tools use the token. Given the 14-parameter nested schema, it also covers tax behavior, currency constraints, error recovery and the fact that Workeey does not verify businesses or quotes. Nothing essential for correct invocation appears missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds cross-field meaning not captured in the schema: use only prices the user gave or a starting price from price_check that they agreed to, never invent one, confirm details before publishing, and never send totals because Workeey adds them up. It also clarifies that customer.name is a display name only and must never be the customer's phone, email or address. The schema already documents most individual fields, so this is a strong 4 rather than a 5.

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?

The description opens with a specific verb and resource ('Create a Quote Link') and immediately explains what the artifact is: a web page where the customer sees a quote, picks one of up to 4 options and add-ons, and approves, declines or asks for changes. It explicitly distinguishes this from the in-app estimates feature and from a draft link, so an agent can tell it apart from siblings without opening schemas.

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?

It gives an explicit gating condition: call it ONLY when the user asks to publish the quote, because the page is live immediately. It names the alternative path in detail (price_check's draft_link or the draft URL with encoded JSON) and tells the agent what to do otherwise, which is exactly the when/when-not guidance an agent needs.

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