Skip to main content
Glama

List quotes

list_quotes
Read-onlyIdempotent

Use this when the user asks to see their quotes or proforma invoices, open or accepted quotes, or quotes for a client. Lists quotes and proforma invoices of one business, newest document date first: number, date, valid until, status, client name, currency, total, VAT and the invoice it was converted to. status is one of all, draft, sent, accepted, declined, expired. No client contact details. Do not use it for invoices (list_invoices).

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1 to 50. Default 20.
cursorNonext_cursor from the previous page, with the same filters.
statusNoOne of all, draft, sent, accepted, declined, expired. Default all.
date_toNoYYYY-MM-DD, document date on or before.
client_idNoFrom list_clients.
date_fromNoYYYY-MM-DD, document date on or after.
business_idNoFrom list_businesses. May be left out when the connection shares exactly one business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely non-obvious behavior: newest document date first ordering, the exact fields returned, and the caveat "No client contact details." It stops short of describing page-size or cursor semantics, but those are documented in the schema.

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?

A single front-loaded paragraph that opens with the trigger and closes with the exclusion, so the most decision-relevant information comes first. The re-listing of the six status values duplicates the schema enum and is the one segment that does not fully earn its place.

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 no output schema, the description compensates by enumerating the returned fields (number, date, valid until, status, client name, currency, total, VAT, converted invoice) and the sort order. Combined with full schema coverage on all seven parameters, an agent has everything needed to select and invoke it correctly.

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 description coverage is 100%, so every parameter, including the status enum values and the date formats, is already documented in the schema. The description largely restates the status values and adds only the mild clarification that results are scoped to one business. Baseline 3 applies since the schema does the heavy lifting.

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 ("Lists quotes and proforma invoices of one business") and enumerates the returned fields, so the agent knows exactly what the tool returns. It also names the sibling it is not ("Do not use it for invoices (list_invoices)"), making it distinguishable 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?

Begins with an explicit trigger ("Use this when the user asks to see their quotes or proforma invoices, open or accepted quotes, or quotes for a client") and closes with an explicit exclusion routing to list_invoices. Both the when and the when-not are stated rather than inferred.

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