Skip to main content
Glama

Add or complete customers (preview, then confirm)

accounting_update_customers

Add customers, or fill in MISSING details of existing customers (matched by customer_id, account number or exact name). Nothing already recorded is overwritten. TWO STEPS: first call = preview + confirm_token; the change is only made on the second call with confirm_token. Changes the user's real books — only after they have seen the preview and agreed. Needs the user's GetAccountED sign-in (they are asked to sign in the first time).

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": {
      "rows": "<rows>"
    },
    "name": "accounting_update_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesOne per customer
add_if_newNoAdd customers that do not exist yet (default false)
business_idNoAccounting practices only: which client's books (an id from accounting_list_my_businesses). Leave out to use the books chosen at sign-in.
confirm_tokenNoSecond step only: the token from the preview

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the non-overwrite guarantee, the mandatory preview/confirm two-step, that it mutates the user's real books, and that sign-in is required on first use. These are exactly the behavioral traits an agent needs before invoking a write tool.

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?

Front-loads the core action, then the matching rule, then the safety-critical two-step flow. Dense but every sentence carries information; no filler.

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 mutation tool with no output schema, the description covers the safety profile, the two-step protocol, auth needs, and matching behavior. An agent has everything needed to call it correctly and safely.

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 baseline is 3; the description adds real meaning by explaining the matching semantics for existing customers and the add_if_new gating of new records. It does not elaborate on business_id or confirm_token beyond the schema, but the added matching logic is valuable.

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 ('Add customers, or fill in MISSING details of existing customers') and pins down the matching keys (customer_id, account number, exact name). It is clearly distinguishable from accounting_list_customers, which is the read-only sibling.

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?

Gives explicit when-to-use context: add new vs complete missing details, nothing overwritten, and the two-step preview-then-confirm flow with the condition for the second call. It does not explicitly name a sibling alternative for looking up ids, but the guidance is otherwise clear.

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.