Skip to main content
Glama

quickbooks_list_tax_codes

Retrieve a list of tax codes from your QuickBooks account under your company scope.

Instructions

Quickbooks connector operation list_tax_codes (platform tool quickbooks.list_tax_codes).

Routes through /api/tools/invoke under your JWT, tenant, and company scope.

Args: arguments: JSON string of arguments for the connector operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo{}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided; description only mentions routing details but does not disclose read-only nature, side effects, or auth requirements beyond JWT/scope. For a list tool, transparency is lacking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is relatively short but front-loads technical routing instead of core purpose. The 'Args' line is minimal but functional. Could be more efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists but details are omitted. No information on what tax codes are returned, filtering, or pagination. For a list operation, description is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only parameter 'arguments' is described vaguely as 'JSON string of arguments for the connector operation'. No details on expected keys, values, or format. Schema coverage 0%, and description fails to compensate.

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?

Description clearly states it lists tax codes, but does not differentiate from sibling tool quickbooks_list_tax_rates which has a similar purpose.

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?

No guidance on when to use this tool versus alternatives like quickbooks_list_tax_rates or other QuickBooks list operations. No context on prerequisites or limitations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RPasquale/lightbulb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server