Skip to main content
Glama
Sign In
QuickBooks Online MCP Server

QuickBooks Online MCP Server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

report_inventory_valuation_summary

Generate an Inventory Valuation Summary report to view quantity, cost, and value of inventory items over a chosen date range, grouped by month, quarter, class, or other dimensions.

Instructions

Run an Inventory Valuation Summary report showing quantity, cost, and value of inventory items. Supports date range and summarization.

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": "report_inventory_valuation_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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. It mentions the report's content but does not disclose that the operation is read-only, what permissions are needed, how results are returned, pagination behavior, or whether report generation has side effects. The statement that it 'supports date range and summarization' is a feature note rather than behavioral disclosure.

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?

The definition is two tightly written sentences with the purpose front-loaded and no redundant wording. Every sentence contributes directly to identifying the report's scope and supported features.

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 report tool with no annotations and no output schema, the description is too thin. It should at least clarify read-only behavior, default date semantics, and how summarization affects output; instead it gives only a high-level statement of content and supported inputs.

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 top-level schema description coverage is 0%, and the description only vaguely indicates that date range and summarization are supported. It does not explain the date_macro vs. start_date/end_date mutual exclusivity, date format expectations, or what summarize_column_by controls beyond the high-level phrase 'summarization'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Run') and resource ('Inventory Valuation Summary report') and clarifies the report content: quantity, cost, and value of inventory items. This clearly differentiates it from sibling report tools such as report_item_sales or report_account_list.

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?

Usage is only implied by the report name and stated content; there is no explicit when-to-use guidance, no mention of alternatives, and no prerequisites or exclusions. An agent can infer this is for inventory valuation reporting, but the definition leaves it to inference.

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