stub

Import accounts

import_accounts

Bring a whole chart of accounts in from another package (Xero, Sage, QuickBooks), one row per account with its type. An account the chart already has (Sales, Accounts Receivable, Accounts Payable, VAT, Retained Earnings) is reused, not made twice, so reports read as one chart. Prefer this to create_account for more than one account. Returns a summary to read to the customer.

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": {
      "items": "<items>"
    },
    "name": "import_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	The chart's accounts, one row each, as the old package lists them.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only state readOnly=false and destructive=false; the description adds genuinely useful behavior — existing standard accounts (Sales, Accounts Receivable, VAT, etc.) are matched and reused rather than duplicated, so the operation is idempotent for well-known accounts. It also discloses that a summary is returned to relay to the customer. It does not cover partial-failure or validation behavior, and never states that imported rows cannot be deleted afterwards.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it does, the dedup guarantee, then the routing rule — all front-loaded with no filler. Each sentence adds a distinct decision-relevant fact.

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?

For a single-parameter but structurally nested bulk import with no output schema, the description covers purpose, dedup semantics, sibling routing, and that a summary comes back. It stops short of stating scale limits, ordering/atomicity, or what happens to rows whose type isn't recognized.

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%, with the nested item properties documented including the full list of accepted account types, so the schema carries the parameter burden. The description only adds the framing 'one row per account with its type', which is a baseline-level contribution.

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 ('Bring a whole chart of accounts in from another package') and constrains the shape of the input ('one row per account with its type'), naming the source packages. It also distinguishes itself from create_account, so an agent can route correctly without opening a schema.

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 an explicit selection rule: prefer this over create_account when importing more than one account. What's missing is when-not-to-use guidance or prerequisites (e.g. whether the business needs a chart configured first, or what to do about accounts that don't map to a listed type).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All stub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?