Skip to main content
Glama
Sign In

Tradify MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get quote

get_quote
Read-onlyIdempotent

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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description appropriately focuses on what data is returned. It thoroughly discloses the returned quote structure, including nested lines and invoices, though it does not mention error behavior such as an invalid or missing quote_id.

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 front-loaded with the core return summary and then details fields in a dense but relevant way. There is minor redundancy between the opening summary and the detailed field list, but given the absence of an output schema, most of the content earns its place.

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 simple single-record retrieval tool with one required ID, the description is nearly complete because it documents the return shape in detail and annotations cover the safety profile. The only notable gap is that it does not describe failure behavior or access constraints if the quote is not found.

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?

There is only one parameter, and the schema fully documents it as 'Quote ID from list_quotes.' The description adds no additional parameter meaning beyond the schema, which is acceptable given 100% schema description coverage.

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 states exactly what the tool returns: a full, single quote with its lines, totals, tax, profit, dates, and related invoices. The phrase 'Returns one quote' distinguishes this retrieval tool from list-oriented siblings such as list_quotes.

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 implied by 'Full quote' and 'Returns one quote' plus the required quote_id, but the description does not explicitly say when to use this tool versus list_quotes or other quote-related tools. It gives no exclusions or workflow guidance beyond the return scope.

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

All Tradify MCP Server and API by Cotlet toolsInspect
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