Groundbase

Manage quotes

quotes_manage

Destructive

Quotes. save_draft (create, or edit by id), issue (numbers it), send (emails it with an accept link; confirm), record_outcome (accepted / declined after a conversation), convert (accepted → draft invoice), void, public_link (the accept link; revoke).

Input Schema

Name	Required	Description
`id`	No	Required for: issue, send, record_outcome, convert, void, public_link; optional for: save_draft. Edit this draft.
`to`	No	Default: billing email, then the contact's email.
`lines`	No	itemId (saved item) or name + unitPrice. Decimal strings. taxIds: which of the taxes apply (default all).
`notes`	No
`taxes`	No	[{id?,name,rate}], e.g. GST 5 + QST 9.975 (ids t1,t2…).
`terms`	No	What the customer agrees to by accepting.
`action`	Yes
`reason`	No	Declined: optional reason.
`revoke`	No	public_link: turn the link off.
`charges`	No	Below the subtotal (shipping); negative for a discount or deposit.
`message`	No	Covering note; same tokens.
`outcome`	No
`sendVia`	No
`subject`	No	Tokens {number} {business} {customer} {amount} {due}.
`currency`	No	ISO 4217. Defaults from the billing profile.
`companyId`	No
`contactId`	No	Create: one of contactId/companyId.
`issueDate`	No	YYYY-MM-DD. Default today.
`validUntil`	No	YYYY-MM-DD. Default issue date + 30 days.
`confirm_paid`	No	Void despite a deposit.
`depositAmount`	No	e.g. "500.00". Empty string removes.
`acceptedByName`	No	Accepted: who said yes, e.g. "Dana (by phone)".
`depositPercent`	No	e.g. "25". Empty string removes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 18, 2026

changedInput schema / properties / charges / description

Previous value: -"Charges below the subtotal (shipping, rush fee); a negative amount for a deposit or discount."New value: +"Below the subtotal (shipping); negative for a discount or deposit."

removedInput schema / properties / charges / items / properties / amount / description
```
Removed value: -"Decimal string."
```

changedInput schema / properties / lines / description

Previous value: -"Line items: itemId (saved item, priced in this currency) or name + unitPrice for a one-off. Amounts are decimal strings."New value: +"itemId (saved item) or name + unitPrice. Decimal strings. taxIds: which of the taxes apply (default all)."

removedInput schema / properties / lines / items / properties / quantity / description
```
Removed value: -"e.g. \"1.5\"."
```

addedInput schema / properties / lines / items / properties / taxIds

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / lines / items / properties / taxRate / description
```
Removed value: -"Percent, e.g. \"17.5\". Defaults from the item."
```

addedInput schema / properties / taxes

Added value: +{
+  "description": "[{id?,name,rate}], e.g. GST 5 + QST 9.975 (ids t1,t2…).",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / confirm_paid

Added value: +{
+  "description": "Void despite a deposit.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / id / description

Previous value: -"Edit this draft. Omit to create."New value: +"Required for: issue, send, record_outcome, convert, void, public_link; optional for: save_draft. Edit this draft."

AddedOct 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations, it discloses important behavior: send emails the quote externally with an accept link and requires confirmation, convert creates a draft invoice, and public_link can be revoked. This aligns with the destructive/open-world annotations, though it does not cover permission requirements, rate limits, or return behavior.

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 a single dense sentence that front-loads the resource and then lists every action with a compact effect. There is essentially no wasted text.

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 23-parameter action multiplexer with no output schema, it covers the most important selection context: every action and its key side effect. The schema carries parameter details and annotations carry the safety profile, but return values and some per-action prerequisites remain implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high at 78%, so the schema already documents most parameters. The description adds material meaning for the central action parameter by explaining what each enum value does, which the schema enum alone does not provide. It does not add much for the other 22 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and enumerates all seven lifecycle actions with specific effects: save_draft creates/edits, issue numbers, send emails, record_outcome records acceptance/decline, convert makes a draft invoice, void, and public_link manages the accept link. It is clear enough to distinguish this from a read-only quotes tool, though it never explicitly names quotes_list as the sibling for listing.

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?

It gives clear action-level context: record_outcome is for use after a conversation, convert applies to accepted quotes and produces a draft invoice, send includes a confirmation, and public_link can be revoked. It does not explicitly state when to use this tool versus quotes_list or invoices_manage, so it is clear but lacks exclusions/alternatives.

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

All Groundbase tools Inspect

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

Need Help?