data Static interface comparison
Ekwo OS — open source accounting: ledger, invoices and VAT on your own Supabase or Postgres
0.24.1 0.25.0
3 schema changes require review.No new authority detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 1Added tools
- 0Removed tools
- 4Modified tools
- 3Input-schema changes
- 0Output-schema changes
- 0Declared authority changes
5 tools with recorded changes
contact_statementAddedWhat changed
- New read-only tool contact_statement.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (0.24.1) Current (0.25.0) Change (schema root)not present object - Added
company_idnot present string, format="uuid", pattern="^([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)$"required - Added
contact_idnot present string, format="uuid", pattern="^([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)$"required - Added
fromnot present string, pattern="^\\d{4}-\\d{2}-\\d{2}$"required - Added
tonot present string, pattern="^\\d{4}-\\d{2}-\\d{2}$"required - Added
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_bank_accountModifiedWhat changed
- create_bank_account: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousRegisters a bank account of the company from its identifier — an IBAN, an ABA routing number and an account number, a sort code and an account number, whatever the banks of the company's country use; the pack of the country says which, and it is checked — and wires it to the bank journal and to the ledger account behind it — both of which the country template has already chosen, so neither has to be given. Running it twice with the same identifier returns the one that exists rather than creating a second. Do this once per account: until a company has one, an invoice carries no account to pay into and record_payment can only book on the journal's default account.
- CurrentRegisters a bank account of the company from its identifier — an IBAN, an ABA routing number and an account number, a sort code and an account number, whatever the banks of the company's country use; the pack of the country says which, and it is checked — and wires it to the bank journal and to the ledger account behind it — both of which the country template has already chosen, so neither has to be given. Running it twice with the same identifier returns the one that exists rather than creating a second; a name another account already carries is refused (bank_account_exists), so ask the user for a label when a company has several accounts. The schema's create_bank_account() does the work, the same function a web application calls. Do this once per account: until a company has one, an invoice carries no account to pay into and record_payment can only book on the journal's default account.
Input schema
Input schema unchanged.
12 unchanged entries
(schema root)account_codeaccount_idaccount_identifierbank_namebiccompany_idcurrency_codeibanjournal_codejournal_idlabel
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
render_invoice_pdfModifiedWhat changed
- render_invoice_pdf — Schema change: input property labels changed: description "The words the layo… → "Words the layout p….
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- read → read
Input schema
Property Previous (0.24.1) Current (0.25.0) Change labelsobject, additionalProperties {…}, propertyNames {…}optional object, additionalProperties {…}, propertyNames {…}optional - Description changed
4 unchanged entries
(schema root)document_idfactur_xpage_size
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
suggest_duplicate_contactsModifiedWhat changed
- suggest_duplicate_contacts — Schema change: input property added: contact_types.
- suggest_duplicate_contacts: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousThe active contacts of a company that are probably one party — two spellings of one customer, two imports of one supplier — strongest first, one row per contact to absorb. The rows that share a keep_id are one group (the contacts a chain of pairs joins); each names the contact to keep (the one of the group more ledger lines and documents name, then the older), the one to absorb, proposed_name (the simplest name the group carries — the fewest words carried by contacts outside the group, then the fewest words — a proposal for the kept contact, written only if the user wants it), a score from 0 to 1, the kinds of evidence (vat_number, registration_number, account: the same number or bank account, score 1; name: the words of the shorter name in the longer, each weighed by how few contacts carry it, so that a shared trade, place or legal form alone is never a pair; 0.950 for the same name, 0.900 otherwise, 0.600 when the shorter name agrees with several contacts) and the evidence in sentences. Two contacts with different VAT or registration numbers, a contact and its own parent, and inactive or merged contacts are never proposed. It writes nothing: show the user both contacts and call merge_contacts only on a pair they confirm, with the contact they choose to keep.
- CurrentThe active contacts of a company that are probably one party — two spellings of one customer, two imports of one supplier — strongest first, one row per contact to absorb. The rows that share a keep_id are one group (the contacts a chain of pairs joins); each names the contact to keep (the one of the group more ledger lines and documents name, then the older), the one to absorb, proposed_name (the simplest name the group carries — the fewest words carried by contacts outside the group, then the fewest words — a proposal for the kept contact, written only if the user wants it), a score from 0 to 1, the kinds of evidence (vat_number, registration_number, account: the same number or bank account, score 1; name: the words of the shorter name in the longer, each weighed by how few contacts carry it, so that a shared trade, place or legal form alone is never a pair; 0.950 for the same name, 0.900 otherwise, 0.600 when the shorter name agrees with several contacts) and the evidence in sentences. Two contacts with different VAT or registration numbers, a contact and its own parent, and inactive or merged contacts are never proposed. contact_types keeps the proposals among the contacts of those types — customer, supplier and both for the parties of the books — and every contact is read when it is absent. It writes nothing: show the user both contacts and call merge_contacts only on a pair they confirm, with the contact they choose to keep.
Input schema
Property Previous (0.24.1) Current (0.25.0) Change contact_typesnot present array, minItems=1optional - Added
contact_types › [items]not present string, enum (5) - Added
2 unchanged entries
(schema root)company_id
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
update_company_profileModifiedWhat changed
- update_company_profile — Schema change: input property added: invoice_late_payment_mention.
- update_company_profile: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousChanges what a company says about itself on its documents: the names it goes by, its address and identifiers, its logo and the colour, logo side and typeface of its invoice PDF, the pattern of its document numbers, its stated capital, its activity code and the bank account customers are asked to pay into — and agent_posting, how agents post its documents, which you only ever make stricter. Only the fields you name change. It touches nothing in the ledger, and it needs company.write — the owner preset, not the accountant one.
- CurrentChanges what a company says about itself on its documents: the names it goes by, its address and identifiers, its logo and the colour, logo side and typeface of its invoice PDF, whether its invoices print the late payment mention of its country, the pattern of its document numbers, its stated capital, its activity code and the bank account customers are asked to pay into — and agent_posting, how agents post its documents, which you only ever make stricter. Only the fields you name change. It touches nothing in the ledger, and it needs company.write — the owner preset, not the accountant one.
Input schema
Property Previous (0.24.1) Current (0.25.0) Change invoice_late_payment_mentionnot present booleanoptional - Added
29 unchanged entries
(schema root)activity_codeactivity_descriptionactivity_schemeaddress_line1address_line2agent_postingcitycompany_iddefault_bank_account_iddocument_templateemailidentifiersinvoice_accent_colorinvoice_logo_positioninvoice_typefacelegal_formlegal_namelogo_urlnamenumber_formatphonepostal_coderegistration_numbershare_capitalshare_capital_currencytrade_namevat_numberwebsite
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
72 tools with no recorded change
aged_balanceanalytic_reportcancel_documentclose_fiscal_yearclose_fiscal_year_finallycreate_api_keycreate_bank_transactioncreate_companycreate_contactcreate_documentcreate_productdescribe_packec_sales_listfinancial_analysisfinancial_statementgeneral_ledgergenerate_fecget_companyget_documentget_preferencesimport_bank_statementimport_booksinstalment_planinvite_memberjournal_bookleave_line_unnamedlist_accountslist_analytic_axeslist_api_keyslist_bank_accountslist_bank_transactionslist_companieslist_documentslist_invitationslist_shareslist_statementslock_periodmatching_difference_optionsmerge_contactsopening_balancepin_accountsportfolio_filings_touched_sinceportfolio_upcoming_filingspost_documentread_audit_logreconcilereconcile_manyreconcile_with_differencerecord_paymentremove_memberreopen_fiscal_yearreverse_entryrevoke_api_keyrevoke_invitationrevoke_sharesearch_contactssearch_productsset_line_contactset_member_roleset_number_prefixset_preferencessettle_from_statementshare_documentstatussuggest_item_combinationssuggest_line_contactstrial_balanceundo_leave_line_unnamedunreconcileupdate_document_linesupdate_productvat_return
Evidence and provenance
- Static findings
- REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Pending human review. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
ekwo-mcp/0.24.1~0.25.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 11:32 PM UTC.- Distribution
npm- Previous release
@ekwo-ai/mcp@0.24.176 tools · published by the registry Nov 4, 2026, 5:13 PM UTCArtifact integritysha512-EJN8pbvRhrAE5u51mpxRXj7/5emUD2sXocZ5L/N5J0AZN7HB+h+C5DTzeoBgPeZUiCO492zL3s5j7tzqWu6ObA==Interface fingerprintsha256:87b90f29ffcab0b8a132be25e20a41b7b6edbbd9ead4eb2c0058befdb1590525Exact interface snapshot (JSON)- Current release
@ekwo-ai/mcp@0.25.077 tools · published by the registry Nov 7, 2026, 7:35 AM UTCArtifact integritysha512-B5GmvagZV2Mf4QLm3F8elAMcnvapau9VJLM7EsulyO8PgnJ1twR5Q7JLQ+HErqfUf9Ysa22ZG/3mtmtdl8+Ldg==Interface fingerprintsha256:1a615c22cbbab41b226d6eb7401d31c84baca5bf0215044fbb44df5196528183Exact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Requires review
3 findingsrender_invoice_pdfREVIEWChangedShow details
input property labels changed: description "The words the layo… → "Words the layout p…
suggest_duplicate_contactsREVIEWChangedShow details
input property added: contact_types
update_company_profileREVIEWChangedShow details
input property added: invoice_late_payment_mention
Informational
4 findingscontact_statementINFOAddedcreate_bank_accountINFOChangedsuggest_duplicate_contactsINFOChangedupdate_company_profileINFOChanged
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.