Skip to main content
Glama
Sign In
QuickBooks Online MCP Server

QuickBooks Online MCP Server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-bill

Retrieves a bill by ID from QuickBooks Online, returning its details so you can review or use a specific vendor bill in your workflow.

Instructions

Get a bill 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-bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses almost nothing. It does not say the operation is a non-mutating read, what happens when the ID does not exist, whether it requires specific QuickBooks permissions, or anything about error/empty responses.

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

Conciseness4/5

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

One front-loaded sentence with no filler words; the resource and lookup key appear immediately. It is efficient, though the brevity borders on under-specification given the absent annotations and undocumented parameter.

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?

For a tool with a nested params wrapper, 0% parameter documentation, no annotations, and no output schema, the description is too thin. The agent gets no information about the returned bill representation, failure behavior, or how to form the nested params object.

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%, and the single id string parameter has no description in the schema. The description only restates that the lookup is "by ID" and does not clarify the expected ID format, whether it is the QuickBooks internal ID, or how it is nested inside the required params wrapper object.

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?

"Get a bill by ID" states a specific verb (get), resource (bill), and lookup key (ID), and naming the ID lookup implicitly separates it from search_bills. It does not explicitly call out that sibling, but the name/description pair is unambiguous against the create-bill/update-bill/delete-bill family.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent must infer that this tool is appropriate only when it already holds a bill ID and that search_bills is the path otherwise, which is a reasonable inference but not stated.

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