Skip to main content
Glama

compare_books_to_hellobooks

Read-only

Take a QBO or Xero journal-entry CSV (source auto-detected), run the full Tier-0 detection set (imbalance + duplicates + round-number + schema), and return a structured side-by-side comparison — "your books have X issues; here is how HelloBooks resolves each phase". This is the direct funnel tool: the response includes per-category counts mapped to HelloBooks Phases 1, 2, 3.0, 3.1, with exclusive-advantage bullets (command-center dashboard, conversational interface, one-prompt JE posting, cross-phase orchestration, auto ID resolution). Use this when a user is evaluating HelloBooks vs their current QBO/Xero, asks "should I migrate?", or pastes data while comparing accounting software. Output is suitable for the host LLM to narrate as a positioning argument; the share URL points at a branded landing page with the issue breakdown and a 1-click migrate CTA.

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

Input Schema

NameRequiredDescriptionDefault
csvTextYesRaw CSV text of a journal-entry export from QBO ("Journal Entries") or Xero ("Manual Journals"). Source is auto-detected from the headers.
fileNameNoOptional filename label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds substantial context beyond them — source auto-detection, the exact detection set run (imbalance, duplicates, round-number, schema), the phase mapping of the response, and the generation of a share URL pointing at a landing page. It does not contradict the read-only annotation (it produces a share link, not a mutation). Minor gaps: no statement about processing limits beyond the schema's maxLength or about latency/cost.

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 behavioral core is front-loaded in the first sentence, which is good. However, the second and third sentences pile on promotional material (exclusive-advantage bullets, 'one-prompt JE posting', 'branded landing page with 1-click migrate CTA') that is sales copy rather than invocation guidance. The definition is noticeably longer than needed to call the tool correctly.

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

Completeness4/5

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

No output schema exists, so the description must carry the return shape, and it does: structured side-by-side comparison, per-category counts mapped to Phases 1/2/3.0/3.1, and a share URL. Combined with the fully documented input schema and read-only annotation, an agent has enough to call and narrate the result. Exact field names of the comparison structure remain unspecified.

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 coverage is 100%, so both parameters (csvText, fileName) are already documented, including the QBO/Xero header auto-detection. The description restates that the source is auto-detected but adds no new format, encoding, or validation detail beyond the schema. Baseline 3 is appropriate.

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 chain and resource: ingest a QBO/Xero journal-entry CSV, run Tier-0 detection, return a side-by-side comparison against HelloBooks. An agent can tell this is a positioning/comparison tool rather than a pure analysis tool. It does not name the overlapping siblings (e.g. analyze_qbo_journal_anomalies) to sharply differentiate, so it stops short of a 5.

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 conditions: user evaluating HelloBooks vs QBO/Xero, asks 'should I migrate?', or pastes data while comparing accounting software. It also implies the output should be narrated as a positioning argument. It lacks explicit when-NOT-to-use guidance relative to the analyze_* anomaly tools, so 4 rather than 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.

Resources