QuickBooks Online MCP Server

get_term

Retrieves a QuickBooks Online payment term by ID, giving you due-date rules and term details for invoices and bills.

Instructions

Retrieve a specific payment term from QuickBooks Online by ID.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. "Retrieve" does convey read-only, non-destructive semantics, which is the most important behavioral trait here, but nothing is said about not-found handling, required permissions, or record visibility scope.

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?

A single front-loaded sentence with the verb, resource, source system, and lookup key all present. No filler, no repetition of the tool name.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, the definition is minimally sufficient to invoke it correctly. It is incomplete on how to obtain the ID and on failure behavior, which matter for an agent operating against a large sibling set of term tools.

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?

Schema description coverage is effectively 0% beyond the tautological "Term ID". The description's "by ID" adds nothing further, and it does not say where an ID comes from (e.g., search_terms) or whether any optional fields exist in the open additionalProperties object.

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 uses a specific verb and resource ("Retrieve a specific payment term") and scopes it to QuickBooks Online, so the agent knows exactly what entity is fetched. It stops short of differentiating from sibling search_terms, so an agent must infer that this is the by-ID single-record variant.

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?

"by ID" implies the usage condition: call this when a term ID is already known. There is no explicit guidance to use search_terms when the ID is unknown, and no note about what happens on an invalid or missing ID, so usage is only implied rather than stated.

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

Deploy Server