QuickBooks Online MCP Server

get_payment

Fetch a single QuickBooks Online payment by ID to review its details for reconciliation, reporting, or customer account checks.

Instructions

Get a single payment by ID from QuickBooks Online.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "get_payment"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read operation and 'single payment' clarifies scope, but the description does not state permissions, not-found behavior, whether the call is read-only, or what is returned.

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?

The description is a single front-loaded sentence with no wasted words. It is concise to the point of being sparse, but the structure itself is clean and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool this is nearly enough to invoke, but there is no output schema and the description does not describe the returned payment object, error cases, or authentication expectations. Given no annotations and no output schema, the definition leaves meaningful context gaps.

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

Parameters2/5

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

The schema has low description coverage, so the description must compensate, but it only says 'by ID' and does not explain the nested 'params' object, the expected ID format, or whether the ID is a QuickBooks integer/string identifier. The schema's own id description helps, but the description adds little beyond restating the parameter's purpose.

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 states a specific verb and resource: 'Get a single payment by ID from QuickBooks Online.' This clearly distinguishes it from search_payments, update_payment, and delete_payment by specifying a single-resource retrieval by ID. It stops short of naming sibling alternatives explicitly, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by ID' implies the tool should be used when a payment ID is already known, and the 'single payment' framing implies it is not a search tool. However, there is no explicit guidance to use search_payments when the ID is unknown, nor any stated prerequisites.

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

Deploy Server