quotes_listList quotes with counts per status and open value per currency, or pass id for one quote with lines, totals, deposit and acceptance details.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Quote id. Returns that one quote. | |
| limit | No | Default 100. | |
| offset | No | ||
| status | No | draft | open | accepted | declined | void | expired (open but past valid-until) | |
| companyId | No | ||
| contactId | No |
Changes observed during successful MCP inspections.
Input schema / properties / limitAdded value: +{
+ "description": "Default 100.",
+ "maximum": 500,
+ "minimum": 1,
+ "type": "integer"
+}Input schema / properties / offsetAdded value: +{
+ "minimum": 0,
+ "type": "integer"
+}Input schema / properties / companyId / descriptionRemoved value: -"Only quotes for this company."Input schema / properties / contactId / descriptionRemoved value: -"Only quotes for this contact."Input schema / properties / idAdded value: +{
+ "description": "Quote id. Returns that one quote.",
+ "type": "string"
+}Input schema / properties / status / descriptionPrevious value: -"draft | open | accepted | declined | void | expired"New value: +"draft | open | accepted | declined | void | expired (open but past valid-until)"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds valuable behavioral context about what the list returns (counts per status and open value per currency) and what the single-quote mode includes (lines, totals, deposit, acceptance details).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no wasted language. The list mode and the `id`-based detail mode are both stated compactly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Because there is no output schema, the description usefully explains what both modes return. It is nearly complete for a read-only list/retrieve tool, though it leaves some filter and pagination parameters unexplained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 50%, so the description should compensate for undocumented parameters. It clarifies `id` behavior, but it does not explain `offset`, `companyId`, or `contactId`, nor does it describe filtering or pagination behavior beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource and distinguishes two modes: listing quotes versus passing `id` to retrieve one quote. It does not explicitly distinguish itself from `quotes_manage`, but the read-only purpose is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description tells the agent when to pass `id` for the single-quote mode versus using the list mode. It provides clear context for mode selection but does not explicitly state exclusions or point to `quotes_manage` for writes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.