QuickBooks Online MCP Server

get_tax_agency

Retrieve a specific QuickBooks Online tax agency by its ID to view agency details for tax reporting, reconciliation, or account setup.

Instructions

Retrieve a specific tax agency 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_tax_agency"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It does not say whether the call is read-only, what happens if the ID does not exist (error vs empty), whether permissions or scopes are required, or what object shape comes back, and there is no output schema to fall back on.

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?

A single front-loaded sentence with zero filler, which is appropriate for a simple getter. It is lean to the point of under-specification, but no wording is wasted.

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 description is enough to identify the operation and the key. It stops short of the things an agent would still need to call it confidently: failure behavior on an invalid ID and any hint about the returned record.

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?

The schema declares a single required 'id' string with the terse description 'Tax agency ID', and the tool description adds only the phrase 'by ID'. With one obvious parameter this is minimally sufficient, but nothing is said about ID format, source, or whether the nested params wrapper accepts additional properties.

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?

States a specific verb (retrieve), resource (tax agency), source system (QuickBooks Online), and lookup key (by ID). It implicitly separates itself from the sibling search_tax_agencies by emphasizing single-record retrieval by ID, though it never names that sibling explicitly.

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 is for when an identifier is already known, which hints at the search-vs-get distinction. However, no alternative tool is named and there is no guidance on what to do when the ID is unknown or where an ID comes from.

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

Deploy Server