Skip to main content
Glama

HelloBooks AI Agents MCP Server

analyze_xero_journal_cleanup

Read-only

Scan a Xero "Manual Journals" CSV export for cleanup issues — unbalanced journals, duplicate journals (same date + same totals), and schema problems (invalid dates, malformed amounts, missing account code/name, missing group key). Input is the raw CSV content the user pastes after exporting from Xero via Accounting → Advanced → Manual Journals → Export. Xero-specific idioms handled: signed Amount column (positive = credit, negative = debit), explicit Debit/Credit fallback shape, Reference-or-Narration+Date grouping, account code preferred over name. Max 5,000 rows; max 5 MB. Returns structured flags with severity, a roll-up summary, parse diagnostics, and a shareable URL at agents.hellobooks.ai/r/{slug}. Use this when a user pastes Xero manual-journal data, asks "check my Xero books", or "find issues in my Xero journal". The funnel CTA routes to /migrate/from-xero for users who want to fix at scale.

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_xero_journal_cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvTextYesRaw CSV text of a Xero "Manual Journals" report. Export from Xero: Accounting → Advanced → Manual Journals → Export. 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

A4.3/5.0
Behavior5/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 behavior on top: hard limits (5,000 rows, 5 MB), the returned payload (severity-tagged flags, roll-up summary, parse diagnostics, shareable URL), and the Xero idioms it tolerates (signed Amount, Debit/Credit fallback, Reference-or-Narration+Date grouping, code over name). That is exactly the context an agent needs to predict what happens on invocation.

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 purpose and scope, then limits, then triggers — a sensible ordering with dense but non-repetitive sentences. The closing funnel sentence about /migrate/from-xero is marketing context rather than invocation guidance and slightly dilutes the payload, though it is only one line.

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?

There is no output schema, and the description compensates by describing the return shape (flags with severity, roll-up, diagnostics, share URL). Combined with input limits, accepted formats, and use triggers, nothing material is missing for a two-parameter read-only analysis tool.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents csvText and fileName, establishing a baseline of 3. The description goes beyond it by specifying which CSV shapes are accepted (signed Amount vs. explicit Debit/Credit columns) and that the input is the raw pasted file content, which meaningfully constrains what the agent should pass.

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?

The description opens with a specific verb and resource ('Scan a Xero "Manual Journals" CSV export') and enumerates the exact issue classes it detects: unbalanced journals, duplicate journals (same date + same totals), and schema problems. Platform scoping to Xero implicitly separates it from the QBO sibling, but no sibling is named explicitly, so differentiation stops just 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?

It gives concrete trigger phrases: 'when a user pastes Xero manual-journal data, asks "check my Xero books", or "find issues in my Xero journal"'. That is clear when-to-use guidance. It never states when NOT to use it or names an alternative such as analyze_xero_journal_anomalies, so there is no explicit exclusion or routing between the two analysis tools.

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.