Skip to main content
Glama

Get quote

get_quote
Read-onlyIdempotent

Retrieves a single Tradify quote with its status, customer, line items, pricing, tax, totals, gross profit and linked invoices. Use it to review quote details by quote ID.

Instructions

Full quote: lines with price and cost, tax, totals, gross profit, dates and invoices made from it.

Returns one quote: status (draft, awaiting_acceptance, accepted, declined, cancelled, expired), customer, job, reference, description, quote, expiry and acceptance dates, its lines (item, time, misc or kit, with quantity, unit price, unit cost, tax rate and amount), subtotal, tax, total, cost and gross profit, and the invoices made from it so far.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesQuote ID from list_quotes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

The readOnly, idempotent, and non-destructive annotations already cover safety behavior. The description adds meaningful return-shape context, including status values and the linked invoices, which is valuable because there is no output schema; it does not discuss error/not-found behavior, keeping it from a 5.

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?

The description is front-loaded with the summary 'Full quote' and then supplies the needed detail efficiently. The enumeration is dense but justified because no output schema exists.

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?

With one fully documented parameter, read-only annotations, and no output schema, the description carries the return-value burden well by naming the major quote fields and linked invoices. Nothing essential for correct invocation 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%, so the sole parameter is already fully documented. The description does not add further parameter syntax or meaning beyond what the schema provides, which matches the baseline 3.

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 uses a specific verb/resource framing ('Full quote') and enumerates exactly what is returned, which makes its scope distinct from list_quotes and from get_invoice. An agent can tell this retrieves one complete quote rather than a list or a partial summary.

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 description makes clear this returns a single quote, and the schema parameter explicitly points to 'Quote ID from list_quotes', giving a clear usage path. It does not explicitly name alternatives or exclusions, so it stops short of a 5.

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