Skip to main content
Glama

migration_checklist

Read-only

A phased, best-practice plan for moving to HelloBooks from another system. Pass from (quickbooks/xero/tally/zoho-books/wave/sage/excel/other), optional country (adds the right tax-setup step), complexity (low/medium/high — scales phase durations), and includeHistory. Returns 7 ordered phases (plan → export → clean & map → set up → import → reconcile → parallel run & cutover), each with concrete steps and a day-range, plus an estimated total timeline. Complements estimate_migration_effort (which quotes hours/price from an uploaded CSV). Guidance, not a binding plan.

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": {
      "from": "<from>"
    },
    "name": "migration_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe software being migrated from.
countryNoISO country code, for the tax-setup step.
complexityNoScales phase durations. Default medium.
includeHistoryNoWhether to migrate full transaction history (vs opening balances only). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the exact return structure (7 ordered phases with day ranges plus a total timeline) and its non-authoritative nature, since no output schema exists to convey this.

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 and dense with useful content, but the sentence re-enumerates the `from` enum values that the schema already carries verbatim and spends a clause on each parameter. Slight redundancy against a schema that documents everything, but no wasted framing.

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?

For a read-only, no-output-schema tool with four well-documented params, the description covers what it does, what it returns, how phase durations respond to inputs, and how it differs from the alternative. An agent has everything needed to select and call it correctly.

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 3 is the floor, but the description goes further for two params: country 'adds the right tax-setup step' and complexity 'scales phase durations,' explaining downstream effects not visible in the schema. includeHistory is left to the schema's own description, which is adequate.

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 resource and output shape: a phased migration plan with 7 named ordered phases and a total timeline. It explicitly names the sibling it is not (estimate_migration_effort, which quotes hours/price from an uploaded CSV), so an agent can distinguish the two without inspecting schemas.

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?

Routes the agent precisely: use this for a best-practice plan, use estimate_migration_effort for a CSV-derived hour/price quote. It also sets the expectation boundary with 'Guidance, not a binding plan,' which tells the agent how much weight to give the output.

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