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

Keep an estimate

tax_record_computation

Keeps what tax_estimate says now as the next computation of the year, numbered, with its lines, so that it can be read again after the ledger moves. It stays an estimate: calling a computation final is the owner's act, outside this server, and only a final one names the tax due. Writes nothing to the ledger. Record only when the user asks.

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": {
      "company_id": "<company_id>",
      "fiscal_year_id": "<fiscal_year_id>"
    },
    "name": "tax_record_computation"
  }
}

Input Schema

Name	Required	Description
`at`	No	Read the ledger as it stands on this day. Left out, the whole year.
`company_id`	Yes	The company to work in. Ask list_companies if unsure.
`fiscal_year_id`	Yes	The financial year. get_company lists them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 27, 2026

addedInput schema / properties / at / description

Added value: +"Read the ledger as it stands on this day. Left out, the whole year."

addedInput schema / properties / at / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

addedInput schema / properties / company_id / description

Added value: +"The company to work in. Ask list_companies if unsure."

addedInput schema / properties / company_id / format
```
Added value: +"uuid"
```

addedInput schema / properties / company_id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

addedInput schema / properties / fiscal_year_id / description

Added value: +"The financial year. get_company lists them."

addedInput schema / properties / fiscal_year_id / format
```
Added value: +"uuid"
```

addedInput schema / properties / fiscal_year_id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

AddedOct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations it discloses the key traits: nothing is written to the ledger, the snapshot survives later ledger changes, the result is numbered and keeps its lines, and the record remains an estimate because only a final computation names tax due. This resolves the tension an agent would otherwise feel between readOnlyHint=false and the 'estimate' framing.

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 tightly packed sentences, front-loaded with the core action, and each carries distinct information (what is captured, what it is not, when to call). The phrase 'after the ledger moves' is slightly metaphorical where plain 'later ledger changes' would be clearer.

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 three-parameter write tool with no output schema and no rich annotations, the definition covers what is stored, that the ledger is untouched, and the estimate/final distinction. It does not state what the call returns (e.g. an identifier or the numbered computation), which would help since no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so per the baseline this starts at 3; the description's 'what tax_estimate says now' additionally clarifies the snapshot semantics behind the optional `at` date, while schema text already explains company_id and fiscal_year_id lookup paths.

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 ('keeps what tax_estimate says now as the next computation of the year, numbered, with its lines'), which tells an agent exactly what is produced and how it differs from tax_estimate (computes) and tax_computations (reads back).

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 an explicit invocation rule ('Record only when the user asks') and explains that making a computation final is the owner's act outside this server, which implicitly routes finalization elsewhere. It does not name the sibling tools an agent might confuse this with, so it stops short of full alternative routing.

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.