Skip to main content
Glama

HelloBooks AI Agents MCP Server

analyze_qbo_journal_cleanup

Read-only

Scan a QuickBooks Online "Journal Entries" CSV export for cleanup issues — unbalanced journals (debits ≠ credits, with severity by deviation), duplicate journals (same date + same totals, likely posted twice), and schema problems (invalid dates, malformed amounts, missing accounts, missing journal numbers). Input is the raw CSV content the user pastes after exporting from QBO via Reports → Accountant → Journal → Export. Max 5,000 rows; max 5 MB. Returns a structured flag list with severity (high/medium/low), a roll-up summary by category and severity, parse diagnostics (column mapping + unmapped columns), and a shareable URL at agents.hellobooks.ai/r/{slug} (7-day TTL) that renders a branded analysis page suitable for sending to a CA or bookkeeper. Use this when a user pastes QBO journal data, asks "check my books", "find issues in my QBO journal", or "what is wrong with my journal entries". Each flag includes a fixableInHellobooks boolean — true means HelloBooks can resolve it automatically in the paid product.

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": {
      "csvText": "<csvText>"
    },
    "name": "analyze_qbo_journal_cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvTextYesRaw CSV text of a QuickBooks Online "Journal Entries" report. Export from QBO: Reports → Accountant → Journal → Export as CSV. Paste the file contents directly.
fileNameNoOptional original filename, used only as a label on the share page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely useful depth: 5,000-row/5 MB limits, the return structure, and a 7-day TTL share URL. However, generating a public shareable link is an external side effect that sits somewhat awkwardly with openWorldHint=false and is not reconciled in the text.

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?

Front-loaded with the core action and issue categories, then limits, then return shape, then trigger phrases — a sensible ordering. It is one dense run-on paragraph and the share-URL and fixableInHellobooks details could be tightened, but no sentence is pure filler.

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

Completeness5/5

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

With no output schema, the description still characterizes the return value precisely (flag list, severity roll-up, parse diagnostics, share URL). For a two-parameter scan tool, limits, input source, outputs, and triggers are all covered; nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so csvText and fileName are already fully documented, including the export path. The description restates the paste-the-CSV input but adds no constraint or format detail beyond the schema (limits live on the schema's maxLength), so baseline 3 applies.

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 ('Scan a QuickBooks Online Journal Entries CSV export') and enumerates the three issue categories it detects (unbalanced, duplicate, schema problems). It does not, however, explicitly differentiate itself from the closely named sibling analyze_qbo_journal_anomalies, so an agent must infer the 'cleanup' vs 'anomalies' distinction.

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

Usage Guidelines4/5

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

Gives concrete triggering contexts ('check my books', 'find issues in my QBO journal', user pasting QBO journal data), which is strong positive guidance. It stops short of stating when not to use it or naming an alternative tool for adjacent tasks, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.