Skip to main content
Glama
Sign In
QuickBooks Online MCP Server

QuickBooks Online MCP Server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_tax_code

Retrieve a specific QuickBooks Online tax code by ID to look up tax details for transactions, reporting, or reconciliation.

Instructions

Retrieve a specific tax code 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_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 disclosure burden. It implies a read-only lookup but says nothing about behavior on an invalid or missing ID (error vs. empty result), required auth/permissions, or whether the response is the full tax code object.

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 short sentence, front-loaded with the verb and resource, with no redundant or filler wording.

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 simple single-parameter read tool with no output schema or annotations, the description is minimally sufficient to invoke it correctly. It is missing error-behavior and return-content context that would help an agent handle a failed lookup.

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?

There is a single parameter 'id' nested under 'params', and the schema already labels it 'Tax code ID'. The description adds no format details (numeric vs. string, QBO ID conventions) beyond that, but with only one straightforward parameter the schema does most of the work.

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 ('Retrieve a specific tax code'), names the source system (QuickBooks Online), and specifies the lookup key ('by ID'). It is clearly distinguishable from search_tax_codes, 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?

'By ID' implicitly signals that this is the path to take when a tax code ID is already known, contrasting with a search flow. However, no explicit when-to-use or when-not-to-use guidance is given, and neither search_tax_codes nor get_tax_rate is mentioned as an alternative.

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

Deploy Server

Other Tools