Kvickd

Spara uppgifter till årsbokslutet

set_arsbokslut_inputs

DestructiveIdempotent

Sparar uppgifter till årsbokslutet och returnerar det på nytt. regime: k1 eller k2 (k1 bara för enskild firma och ideell förening; för enskild firma är det samma val som NE-bilagans förenklade årsbokslut). account_overrides: {konto: post} när ett konto ska redovisas i en annan post (postnycklarna står i post_choices), null återställer. notes: principer (tillägg till texten om redovisningsprinciper), anlaggningar [{post, anskaffningsvarde (kr), nyttjandeperiod}], sakerheter [{slag, belopp}], eventualforpliktelser, ovrigt, obeskattade_reserver (K1 enskild firma). För ekonomisk förening även verksamhet, vasentliga_handelser, efter_balansdagen, forlagsinsatser, nyttjandeperioder (text), medelantal (antal), aterbetalning (kr), medlemmar {start, nya, avgaende}, disposition {utdelning, reservfond, aterbaring} (kr) och revisor {name, firm, date}. signers: [{name, role, date}] ersätter listan. decided_on (ÅÅÅÅ-MM-DD) och place: datering. Hitta aldrig på namn på undertecknare. Scope statutory. Argument: orgnr, year och de delar som ändras.

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": {
      "orgnr": "<orgnr>",
      "year": "<year>"
    },
    "name": "set_arsbokslut_inputs"
  }
}

Input Schema

Name	Required	Description
`year`	Yes
`notes`	No
`orgnr`	Yes	Bolagets organisationsnummer, 10 siffror med eller utan bindestreck, t.ex. 559900-1004. Hämta med list_companies.
`place`	No
`regime`	No
`signers`	No
`decided_on`	No
`account_overrides`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotency and non-read-only, so the description's job is to explain what is actually affected. It does: 'signers ... ersätter listan' (full replacement, an actual destructive effect), 'null återställer' for account_overrides, and 'de delar som ändras' for the rest, plus 'Hitta aldrig på namn på undertecknare'. No permission, validation or error behaviour is described, which keeps this 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and scope are correctly front-loaded in the first clause, but the remainder is a single dense run-on paragraph mixing field definitions, entity-type conditions and guards. A schema of 8 parameters with heavy nesting would read far better as a short structured list, and several parentheses nest conditions inside conditions.

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 an 8-parameter mutation tool with no output schema and thin schema documentation, the description covers every parameter except the obvious year, plus entity-type conditions and replacement/reset semantics. What is missing is where the referenced post keys come from and whether omitted nested keys are merged or replaced — relevant details for an idempotent-but-destructive save.

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 only 13% (orgnr alone), so the description carries most of the burden and largely does: regime, account_overrides semantics, the nested keys of notes (anlaggningar, sakerheter, eventualforplattelser, obeskattade_reserver), signers objects, decided_on format ÅÅÅÅ-MM-DD and place. It is weakened by a dangling reference to 'post_choices', a field that is not in the input schema and whose origin is never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause 'Sparar uppgifter till årsbokslutet och returnerar det på nytt' names a specific verb and resource, so an agent can tell this writes annual-closing (årsbokslut) inputs rather than the annual report or tax forms. It never names the neighbouring tools (set_arsredovisning_inputs, set_ne_bilaga_inputs, read_arsbokslut) explicitly, so the distinction has to be inferred from the domain vocabulary.

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?

Usage conditions are stated per entity form: regime k1 is limited to enskild firma and ideell förening, extra fields apply 'För ekonomisk förening även...', and 'Argument: orgnr, year och de delar som ändras' communicates partial-update semantics. There is no explicit when-not or pointer to a sibling alternative for the other closing documents.

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

All Kvickd 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.

Resources

Need Help?