Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

quickbooks_list_tax_rates

Read-onlyIdempotent

Retrieve tax rates from QuickBooks for your connected account, giving you the data needed for accurate calculations and reporting.

Instructions

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

Routes only through the exact project/account governed connector authority.

Args: arguments: JSON string of arguments for the connector operation. project_id: Authenticated Project UUID. project_ref: Exact project correlation reference. connector_account_ref: Project-bound connector account alias. idempotency_key: Stable business-action identity. effect: Required and must be read; Spring verifies it. approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectYes
argumentsNo{}
project_idNo
project_refNo
approval_refNo
idempotency_keyNo
connector_account_refNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • addedInput schema / properties / approval_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Approval Ref"
+}
    • addedInput schema / properties / connector_account_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Connector Account Ref"
+}
    • addedInput schema / properties / effect
      Added value: +{
+  "const": "read",
+  "title": "Effect",
+  "type": "string"
+}
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Idempotency Key"
+}
    • addedInput schema / properties / project_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Id"
+}
    • addedInput schema / properties / project_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Ref"
+}
    • addedInput schema / required
      Added value: +[
+  "effect"
+]
  2. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint false), the description adds only a vague statement about routing through 'project/account governed connector authority.' It does not describe the response format, pagination behavior, error handling, or any side effects. The annotations cover the basic safety profile, but the description fails to disclose operational behaviors such as whether it returns a list, how to interpret results, or if any non-read actions are triggered.

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?

The description is concise (two sentences plus a parameter list), which is positive, but the parameter list is largely a restatement of the schema and adds little value. The structure is acceptable—description followed by 'Args:'—but the content is sparse and repetitive. It does not waste words, but it also does not use the available space to convey additional useful information.

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

Completeness1/5

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

The description lacks essential context for correct usage. It does not state what the tool returns (e.g., a list of tax rate objects), how to pass filters via 'arguments', or how to interpret the response. There are no examples, no mention of common pitfalls, and no explanation of the relationship between the required 'effect' parameter and the operation. Given the complex connector context and the presence of an output schema, the description is insufficient for an agent to understand the tool's full behavior and constraints.

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?

The description lists each parameter but provides only generic labels that largely repeat the schema (e.g., 'Authenticated Project UUID' for project_id). It does not explain the meaning or purpose of the parameters in the context of listing tax rates. The 'arguments' parameter is described as 'JSON string of arguments' without specifying which arguments are supported or how they filter the list. Schema description coverage is 0%, so the description is the sole source of parameter semantics, yet it fails to add meaningful detail beyond what is already apparent from the parameter names and types.

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 the operation name ('list_tax_rates') and that it is a QuickBooks connector operation, which clearly implies listing tax rate entities. However, it does not explicitly describe what the tool returns or the nature of the list (e.g., all tax rates, filtered). The routing note about 'connector authority' is tangential to purpose, so the clarity is good but not maximally explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives like quickbooks_list_tax_codes or quickbooks_list_accounts. It does not mention typical use cases, required parameters, or how the 'arguments' JSON should be structured. There is no differentiation from sibling read-only list operations, leaving the agent without direction on selection criteria.

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