Ekwo OS — open source accounting: ledger, invoices and VAT on your own Supabase or Postgres

Create a company

create_company

Creates a company on a country pack: its chart of accounts, its journals and its taxes are copied in, its first financial year is opened on the month that country opens one on, and you become its first member. Creating a company is an instance-level act — it needs an instance administrator, and being one is not the same as being on anybody’s books. Ask the user for the country rather than guessing: the wrong answer is a whole chart of accounts.

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": {
      "name": "<name>",
      "country": "<country>"
    },
    "name": "create_company"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`country`	Yes	Which country pack: its chart of accounts, its taxes and its declaration form. list_companies shows what the installation already uses.
`language`	No	Language the books are kept in — it decides the labels of the chart. Left out, the country pack's.
`chart_code`	No	Which chart, where the country offers several.
`fiscal_year`	No	Calendar year the first financial year opens in. Default this year.
`currency_code`	No	Left out, the country pack's.
`fiscal_year_start`	No	First day of it. Left out, the month the country pack opens a year on — and a pack that names none is a refusal, not a January.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedOct 27, 2026
- addedInput schema / properties / chart_code / description
```
Added value: +"Which chart, where the country offers several."
```
- addedInput schema / properties / country / description
```
Added value: +"Which country pack: its chart of accounts, its taxes and its declaration form. list_companies shows what the installation already uses."
```
- addedInput schema / properties / country / maxLength
```
Added value: +2
```
- addedInput schema / properties / country / minLength
```
Added value: +2
```
- addedInput schema / properties / currency_code / description
```
Added value: +"Left out, the country pack's."
```
- addedInput schema / properties / currency_code / maxLength
```
Added value: +3
```
- addedInput schema / properties / currency_code / minLength
```
Added value: +3
```
- addedInput schema / properties / fiscal_year / description
```
Added value: +"Calendar year the first financial year opens in. Default this year."
```
- addedInput schema / properties / fiscal_year / maximum
```
Added value: +2200
```
- addedInput schema / properties / fiscal_year / minimum
```
Added value: +1900
```
- changedInput schema / properties / fiscal_year / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / fiscal_year_start / description
```
Added value: +"First day of it. Left out, the month the country pack opens a year on — and a pack that names none is a refusal, not a January."
```
- addedInput schema / properties / fiscal_year_start / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
- addedInput schema / properties / language / description
```
Added value: +"Language the books are kept in — it decides the labels of the chart. Left out, the country pack's."
```
- addedInput schema / properties / language / maxLength
```
Added value: +2
```
- addedInput schema / properties / language / minLength
```
Added value: +2
```
- addedInput schema / properties / name / minLength
```
Added value: +1
```
First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only set the safety flags; the description goes further by disclosing the side effects (packs copied, fiscal year opened, caller becomes first member), the authorization requirement, and the cost of a wrong country choice. It does not say whether creation is reversible or how to correct a wrong pack, which keeps it just short of a 5.

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?

Three sentences, front-loaded with the effects of the call, then the permission condition, then the one risk-driven instruction. Dense but each sentence carries distinct information; the em-dash clause is slightly ornate but not padding.

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 non-idempotent 7-parameter mutation with no output schema, the description covers effects, prerequisites and the main failure mode. The only omission is what the call returns, which is minor for a creation tool whose result is the new company.

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 86%, so the parameters are already well documented. The description reinforces the country parameter's consequence ('the wrong answer is a whole chart of accounts') and ties chart/journals/FY opening to the country pack, but adds no format or syntax detail beyond the schema. Baseline 3 applies.

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 states a specific verb and resource and enumerates the concrete consequences: chart of accounts, journals and taxes copied in, first financial year opened, membership granted. That distinguishes it from list_companies, get_company and update_company_profile without needing the 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 states a prerequisite (instance administrator, which is explicitly not the same as being on someone's books) and gives procedural guidance to ask the user for the country rather than guessing. It even points to list_companies to see what a pack already uses. There's no sibling alternative to route to, but the when and the precondition are clear.

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

All Ekwo OS — open source accounting: ledger, invoices and VAT on your own Supabase or Postgres 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.