Caribooks (QuickBooks Online)

List what the loops propose

list_proposals

Read-only

List a company's proposed or completed bookkeeping changes, newest first. Returns each proposal's id, action type, approval mode, status, summary and supporting evidence. Pending proposals can be approved or rejected by the user in Caribooks Approvals or through the daily digest link. This tool is read-only and cannot approve or reject proposals.

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_proposals"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No	Keep only the proposals waiting for the user, the ones carried out, or the ones that failed. All of them when left out.
`company`	No	Which connected company. Every company when left out.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and non-destructive. The description adds the crucial behavioral detail that proposals can't be approved/rejected here and points to where they can, plus the ordering (newest first).

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?

Three tight sentences, front-loaded with purpose and ordering, then return fields, then a behavioral boundary. No filler.

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?

No output schema, so describing returned fields is valuable. It covers ordering, status behavior, and action limitations. Could mention default scope details or pagination, but it's sufficient for a 2-parameter read tool.

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 100%, so the baseline is 3. The description's 'proposed or completed' loosely maps to the status enum, but the schema already explains all values and defaults. Little added meaning.

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 (list) and resource (proposed/completed bookkeeping changes), plus ordering. Clearly distinguishes from sibling tools like list_loops or get_changes by naming the exact object returned.

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?

Explains the two statuses visible (proposed or completed) and that pending ones can be acted on elsewhere. It doesn't explicitly name alternatives, but the read-only note steers usage.

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

All Caribooks (QuickBooks Online) 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?