Skip to main content
Glama

HelloBooks AI Agents MCP Server

analyze_xero_journal_anomalies

Read-only

Scan a Xero "Manual Journals" CSV export for anomalies — currently round-number lines (debit or credit amounts that are exact multiples of $1,000, above a $1,000 materiality threshold). Input is raw CSV text from Xero Accounting → Advanced → Manual Journals → Export. Max 5,000 rows; max 5 MB. Returns flagged lines with severity ($100K+ high, $10K+ medium, else low) and a shareable URL. Use this when a user pastes Xero data and asks "any anomalies?", "look for round numbers", or "anything suspicious". Same Tier-0 / paid-product split as the QBO variant — history-aware anomaly checks (GL outliers, vendor history, archived-vendor activity, LLM-narrated suspicious) live in the authenticated MCP / 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_xero_journal_anomalies"
  }
}

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.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with them while adding real context: hard input caps (5,000 rows / 5 MB), severity banding ($100K+ high, $10K+ medium, else low), that output includes a shareable URL, and the word "currently" which signals the detector set is limited. That last point is exactly the kind of capability caveat an agent needs before promising coverage.

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 verb, resource, and detection scope, then limits, then output shape, then usage triggers — a sensible priority order with no filler sentences. Minor redundancy: the Xero export path is repeated from the schema's csvText description.

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 (flagged lines, severity tiers, shareable URL) along with size limits and the paid-tier boundary. For a two-parameter read-only analyzer, an agent has everything needed to decide and call correctly.

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 both csvText and fileName are already documented with their export path and label-only purpose. The description's CSV-origin sentence largely restates the schema's csvText description rather than adding new meaning, so the baseline 3 applies.

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?

States a specific verb and resource ("Scan a Xero Manual Journals CSV export for anomalies") and immediately narrows the detection scope to round-number lines that are exact multiples of $1,000 above a materiality threshold. It is distinguishable from the QBO sibling and from history-aware checks without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("when a user pastes Xero data and asks 'any anomalies?', 'look for round numbers', or 'anything suspicious'") and an explicit boundary: history-aware checks (GL outliers, vendor history, archived-vendor activity, LLM narration) live in the authenticated MCP / paid product. Both the when and the when-not are stated.

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.