Skip to main content
Glama

estimate_migration_effort

Read-only

Take a QBO or Xero journal-entry CSV (source auto-detected) and return a structured migration-effort estimate — row counts, unique-account count, period span, complexity classification (low / medium / high), human-hours estimate, assisted-hours estimate, and an indicative price quote in USD. Heuristic-based — refined against the live entity once the user signs up. Accepts larger files than the other analytical tools (up to 50,000 rows / 20 MB) because no detection runs here, just sizing. Use this when a user is weighing the cost of moving books to HelloBooks, pastes data and asks "how long will migration take?", "what would this cost?", or "is it worth migrating?". The funnel CTA points at /migrate/?ref= to start the assisted flow with the parsed sizing pre-populated.

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

Input Schema

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

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 already establish readOnlyHint=true and openWorldHint=false, and the description still adds substantial context beyond them: the estimate is heuristic and refined against the live entity after signup, the source is auto-detected from headers, and the file ceiling of 50,000 rows / 20 MB is stated even though the schema only encodes the byte limit. It also discloses the downstream funnel destination with its query parameters, so the agent knows this tool feeds a CTA rather than performing a migration.

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?

It is front-loaded with the action and the output list, and every sentence carries information an agent can act on (triggers, limits, heuristics, CTA). It is a single dense paragraph, though, and the long parenthetical output enumeration plus the CTA URL detail could be tightened or split for faster scanning.

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?

With no output schema, the description carries the burden of explaining return values and does so thoroughly, along with size limits and the heuristic caveat. Remaining gaps are the undocumented fileName parameter and the absence of any statement about behavior on malformed or non-QBO/Xero CSVs, which matters for a tool that auto-detects its input format.

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 50%: csvText is documented in the schema and further enriched by the description (auto-detected source, size allowance), but fileName has no description in either place, and the description never explains what it is used for or how it affects the response. That leaves one of two parameters undocumented, so this is baseline rather than compensating value.

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 opens with a specific verb and resource ('Take a QBO or Xero journal-entry CSV ... return a structured migration-effort estimate') and then enumerates the exact outputs: row counts, unique-account count, period span, complexity class, human/assisted hours and a USD quote. It also distinguishes itself from the sibling analytical tools ('no detection runs here, just sizing'), so an agent can tell what it produces versus analyze_journal_variance or analyze_qbo_journal_anomalies.

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?

Usage is stated explicitly with concrete trigger utterances ('how long will migration take?', 'what would this cost?', 'is it worth migrating?'), which is well above the usual implicit guidance. The only gap is that no alternative is named by name for the case where the user actually wants detection/anomaly analysis rather than sizing; that contrast is left as an indirect 'no detection runs here'.

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