Skip to main content
Glama
Sign In
QuickBooks Online MCP Server

QuickBooks Online MCP Server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_tax_rate

Fetch a specific QuickBooks Online tax rate by its ID to confirm rate details for invoices, transactions, and tax calculations.

Instructions

Retrieve a specific tax rate 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_rate"
  }
}

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 supplied, so the description carries the full behavioral burden and does very little with it. 'Retrieve' weakly implies a read-only operation, but there is no statement about permissions, error behavior for an unknown or deleted ID, or what the returned record contains.

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?

One short sentence with the resource and lookup key front-loaded; there is no filler or redundant restatement.

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-record read with no output schema, the description covers the minimum needed to invoke the tool. It still leaves gaps around failure modes and return content that no annotation or output schema fills in.

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 single parameter is a nested object whose only field is 'id', already labelled 'Tax rate ID' in the schema; the description's 'by ID' adds no format, source, or validation detail beyond that. With schema description coverage reported at 0%, the description only partially compensates, confirming the key but not its shape or origin.

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 names a specific verb and resource ('Retrieve a specific tax rate') and adds the lookup key ('by ID'), so an agent knows this is a single-record fetch rather than a list. It does not explicitly contrast with the sibling search_tax_rates, leaving that differentiation implicit.

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 (you already hold a tax rate ID), which is a usable hint. However, the description never names search_tax_rates as the alternative when only a name or code is known, and gives no prerequisites for obtaining an ID.

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