Skip to main content
Glama
Sign In
QuickBooks Online MCP Server

QuickBooks Online MCP Server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_account

Retrieve a single QuickBooks Online account by its ID to view account details for reporting, reconciliation, or financial management.

Instructions

Get a single account 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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Get' signals a read operation, but it says nothing about behavior on an unknown/inactive ID, authentication requirements, or whether the full account record is returned. For a zero-annotation tool this leaves meaningful gaps.

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 zero redundant wording; the operation, cardinality, lookup key, and system are all established immediately.

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?

This is a simple one-parameter read with no output schema, so the description need not explain return fields. However, given no annotations and an opaque nested params object, it should at least note the not-found behavior or that the ID comes from search_accounts; as written it is minimally sufficient.

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?

Schema description coverage is reported as 0%, though the nested 'id' property does carry a short label. The description adds only 'by ID from QuickBooks Online', providing no format hints, ID provenance, or notes on the additionalProperties passthrough. With a single simple parameter, this is marginally adequate.

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 account') plus the lookup key ('by ID') and the source system (QuickBooks Online), so an agent can tell this apart from search_accounts or create_account. It stops short of explicitly naming those siblings, 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 Guidelines2/5

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

The phrase 'by ID' weakly implies you need a known account ID, but there is no explicit when-to-use guidance, no mention of search_accounts as the alternative for finding accounts, and no prerequisites or failure conditions. The agent must infer all routing decisions.

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