Skip to main content
Glama
Sign In
QuickBooks Online MCP Server

QuickBooks Online MCP Server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_estimate

Retrieves a QuickBooks Online estimate by its ID, enabling AI agents to look up specific estimate details for review or follow-up.

Instructions

Get an estimate 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_estimate"
  }
}

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?

With no annotations supplied, the description carries the full burden of behavioral disclosure. It identifies the source system but says nothing about read-only semantics, behavior when the Id is invalid or the estimate is deleted, permissions, or error 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?

A single front-loaded sentence with no wasted words. It is efficiently structured, though its brevity reflects under-specification rather than deliberate economy.

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?

The tool is simple (one required Id), but with no annotations, no output schema, and 0% parameter coverage, the description should explain what is returned (an estimate object), what happens on not-found, and any realm/company context. None of that is present.

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% for the single nested 'id' parameter. The description merely repeats 'by Id' without adding format, example, or meaning (e.g., whether it is the QuickBooks internal estimate Id or a doc number), so it does not compensate for the coverage gap.

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 verb and resource: 'Get an estimate by Id from QuickBooks Online.' The 'by Id' qualifier implicitly distinguishes it from search_estimates and the create/update/delete_estimate siblings, though no sibling is named explicitly.

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 description provides no when-to-use guidance, no prerequisites, and no routing to alternatives such as search_estimates when the Id is unknown. The only implied guidance is the word 'by Id', which an agent must infer.

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