QuickBooks Desktop MCP

Overview Schema Source Related Servers Discussions Admin

qb_list_currencies

Read-only

Retrieves currencies configured in QuickBooks Desktop with ISO codes, active status, and stored exchange rates, with an option to return active currencies only.

Instructions

QuickBooks' currency list (name, ISO code, active, stored exchange rate in home currency per unit). Only meaningful with multicurrency on.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qb_list_currencies"
  }
}

Input Schema

Name	Required	Description	Default
`active_only`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 1, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds the multicurrency prerequisite, which is genuinely useful behavioral context, but says nothing about pagination, empty results, or error behavior; an output schema covers return shape, so a 3 is fair.

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?

Two tight sentences: the resource and its returned fields first, then the prerequisite caveat. No redundant restatement of the name or title, and nothing that could be cut.

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-only tool with an output schema and annotations, the description covers most needs. The remaining gap is the undocumented `active_only` filter, which is the only thing an agent could get wrong when calling it.

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 0%, so the description must carry the burden for the single `active_only` parameter, and it does not mention it at all — an agent must infer from the name whether setting it filters the returned list. The description does explain the semantic meaning of returned fields, but not the input parameter.

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 resource (QuickBooks currency list) and even enumerates the returned fields (name, ISO code, active, exchange rate), which clearly separates it from sibling list tools like qb_list_accounts or qb_list_vendors. The verb 'list' is implied by the noun phrase rather than stated outright, keeping it short of a 5.

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?

'Only meaningful with multicurrency on' is a real gating condition that tells the agent when this tool is applicable, which is more than most list tools offer. However, it names no alternative and gives no guidance on when to prefer a different tool or what to do when multicurrency is off.

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