Skip to main content
Glama

Get a quote

get_quote
Read-onlyIdempotent

Use this when the user asks about one quote or proforma invoice by number or id. One quote or proforma invoice by quote_id or quote_number: client name and TRN, lines, subtotal, VAT, total, status, valid until, and app_url, a link that opens it in Fatura Go. No client contact details. Do not use it to list quotes (list_quotes) or to change one (update_draft_quote).

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": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idNo
business_idNoFrom list_businesses. May be left out when the connection shares exactly one business.
quote_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in disclosure of contents: the exact fields returned and the explicit exclusion of client contact details, plus the meaning of app_url. With no output schema present this is genuinely useful, though it is silent on what happens if neither identifier is supplied or how business_id scoping affects the result.

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?

Guidance is front-loaded and the sentence order (when to use, what returns, what not to use) is logical with no filler. There is minor redundancy: 'by number or id' in the first sentence is restated as 'by quote_id or quote_number' in the second, and the middle sentence is a dense colon list.

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?

Given a read-only lookup with no output schema and only three parameters, the description covers the essentials: what identifies the record, what comes back, and where it routes elsewhere. The remaining gap is the zero-required-parameter case and business_id scoping, which an agent must infer from the schema alone.

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 only 33%, with just business_id documented, so the description has to carry the other two. It signals that quote_id or quote_number are interchangeable lookup keys, but never says whether one takes precedence when both are passed or what error results from supplying neither (required count is 0). It also never mentions business_id, leaving that entirely to the schema.

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 names a specific resource (one quote or proforma invoice) and a specific lookup key (quote_id or quote_number), then enumerates the returned fields. It also distinguishes itself from list_quotes and update_draft_quote, so an agent can pick it without opening the 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?

It states the triggering condition explicitly ('when the user asks about one quote... by number or id') and gives two negative cases with the correct alternative named for each. Nothing is left to inference about when this tool rather than a sibling should be called.

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