Well

Set accounting settings

well_upsert_accounting_settings

Destructive

Set the workspace's accounting configuration: fiscal year start month, first fiscal year start date, country, base currency, accounting framework, and chart-of-accounts confirmation.

Provide only the fields you are changing; omitted fields are left untouched. An empty call (no fields) is refused.

Only a workspace owner or admin may set the accounting configuration. A caller without that role is refused, not silently ignored.

Changing the fiscal year start month moves the whole fiscal calendar, so it is REFUSED when a period is locked or a close is in progress — the tool surfaces that refusal rather than forcing it. When the change is allowed, it soft-deletes the workspace's regenerable DRAFT journal entries so they re-mint on the new coordinates; VALIDATED and LOCKED entries are never touched.

These are accounting-critical values. Confirm each one with the user before calling and never guess them — do not infer a country, currency, framework, or start month the user did not state.

This tool does NOT set the workspace's legal identity (registered name, trade name, tax id, domain): that is owned by well_set_own_company. Use that tool for identity, this one for accounting configuration.

Input Schema

TableJSON Schema

Name	Required	Description
`country`	No	ISO 3166-1 alpha-2 country code.
`workspace_id`	No	Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
`base_currency`	No	ISO 4217 currency code.
`coa_confirmed`	No	Whether the chart of accounts has been confirmed.
`idempotency_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
`accounting_framework`	No	The accounting framework the books follow.
`fiscal_year_start_month`	No	Calendar month (1-12) the fiscal year starts on, or null to clear it.
`first_fiscal_year_start_date`	No	First fiscal year start date as YYYY-MM-DD, or null to clear it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`country`	No
`success`	Yes
`base_currency`	No
`coa_confirmed`	No
`accounting_framework`	No
`fiscal_year_start_month`	No
`first_fiscal_year_start_date`	No

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark this destructive, but the description substantially enriches that signal: it discloses that DRAFT journal entries are soft-deleted and re-minted, VALIDATED/LOCKED entries are never touched, and unauthorized callers are refused rather than silently ignored. This is exactly the kind of behavioral context agents need beyond structured annotations.

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?

The description is front-loaded with the core purpose, then each subsequent sentence covers a distinct operational concern: partial updates, authorization, destructive side effects, confirmation requirements, and scope boundary. There is no filler or redundant restatement of the title.

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?

Given the tool's complexity and the presence of an output schema, the description covers all critical context: authorization, refusal conditions, partial-update behavior, destructive side effects, user confirmation expectations, and the intended boundary with a sibling tool. Nothing an agent needs to safely decide whether and how to call this tool is missing.

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 description coverage is 100%, so the schema already documents each parameter. The description adds valuable cross-parameter semantics: only provided fields are changed, omitted fields are untouched, empty calls are refused, and the workspace must be unambiguous when the token authorizes multiple workspaces. This goes beyond the schema descriptions and helps avoid misuse.

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 names a specific verb and resource: "Set the workspace's accounting configuration" and enumerates the exact fields involved. It also explicitly differentiates this tool from well_set_own_company by stating that identity fields are NOT handled here, which is strong sibling disambiguation.

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?

The description gives explicit when-to-use guidance: use this for accounting configuration and well_set_own_company for identity. It also states preconditions and refusals: owner/admin required, empty calls refused, fiscal-year changes refused when periods are locked, and omitted fields remain untouched. This is much more than an implied usage hint.

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

All Well tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: CRUD for companies, people, and invoices; financial analytics (cash, cost, runway, holdings); connector management and invocation; schema discovery; querying; reconciliation; and contact channel management. No two tools could be confused for the same action.

Naming Consistency5/5

All tools follow the `well_verb_noun` pattern with consistent verb choices (create, get, list, update, delete, add, remove, run, resolve, query, invoke). The naming is predictable and makes the tool's purpose immediately clear.

Tool Count4/5

With 26 tools, the set is slightly above the ideal 3-15 range, but every tool earns its place given the breadth of the domain (CRM, invoicing, financial analytics, reconciliation, connector management). The count is well-scoped and not excessive.

Completeness4/5

The tool surface covers core CRUD, financial KPIs, reconciliation, and connector management. Minor gaps exist (e.g., no direct tool to update contact channels or manage accounts), but the query and schema tools allow agents to work around them, and the primary workflows are fully supported.

Resources

Need Help?