Skip to main content
Glama
Sign In

DigitalK2

by se.digitalk2
OverviewDiscussionsAdmin

Ersätt fält i aktuellt steg

update_fields
DestructiveIdempotent

Ersätter värden i fält i steg 2 till 6, som när användaren skriver i formuläret.

Verktyget ersätter befintliga värden i det aktuella steget: angivna fält skrivs över och listor (t.ex. undertecknare eller periodiseringsfonder) ersätts helt. Ändringen görs i den öppna sidan med samma uppdatering som formuläret använder, så guidens egna kontroller och beräkningar körs som vanligt. Bara fält som finns i read_draft och med samma typ accepteras; ett felaktigt fält gör att inget ändras. Ja/Nej-frågor i steg 3 till 6 (t.ex. ink2Help, activeNotes) sätts här. Fälten i steg 1 fylls i med fill_input. Fråga användaren om uppgifter du inte vet; hitta inte på texter, datum eller namn.

Returnerar applied (ändrade fält) och snapshot efteråt (med messages om något inte stämmer).

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": {
      "draft_id": "<draft_id>",
      "section": "<section>",
      "values": "<values>"
    },
    "name": "update_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYesFälten som ska ändras, med samma namn och struktur som read_draft visar. Objekt slås ihop, listor ersätts helt. Exempel: {"väsentligaHändelser": "Inga väsentliga händelser."} eller {"inputs": {"pf_avsattning": 20000}} eller {"activeNotes": {"E": true}}. Steg 2: {"rows": [{"label": "Nettoomsättning", "currentYear": 500000}]} med exakt label och belopp som de visas i guiden (som read_draft visar dem när utkastet är öppet).
sectionYesVilken del som ändras. Måste vara det steg guiden står på: income_statement och balance_sheet = steg 2, tax = steg 3, management_report = steg 4, notes = steg 5, signature = steg 6. Steg 1 fylls i med upload_sie, fill_input, fetch_company_details och set_first_annual_report.
draft_idYesUtkastets id (draft_id), t.ex. från list_drafts. Utkastet måste tillhöra det anslutna kontot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Vilken del som ändras. Måste vara det steg guiden står på: income_statement och balance_sheet = steg 2, tax = steg 3, management_report = steg 4, notes = steg 5, signature = steg 6. Steg 1 fylls i med upload_sie, fill_input och press_button."New value: +"Vilken del som ändras. Måste vara det steg guiden står på: income_statement och balance_sheet = steg 2, tax = steg 3, management_report = steg 4, notes = steg 5, signature = steg 6. Steg 1 fylls i med upload_sie, fill_input, fetch_company_details och set_first_annual_report."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=false, so the bar is lower, yet the description adds real substance: fields are overwritten, lists are replaced wholesale while objects merge, only fields present in read_draft with a matching type are accepted, and one invalid field aborts the whole change. It also explains the write routes through the same update path as the form so the guide's recalculations run.

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?

Purpose is front-loaded in the first sentence, followed by behavior, validation constraints, routing, and return values in a logical order. It is dense and longer than typical, but each sentence carries operational information rather than filler.

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 destructive, nested-object mutation tool with no output schema, the description covers the return contract (applied plus a snapshot with messages on failure), the overwrite/merge semantics, validation failure behavior, and step ownership. Nothing essential for correct invocation 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 coverage is 100% and the schema descriptions are already detailed, so baseline is 3. The description adds semantic constraints the schema does not state — the read_draft/type-match validation rule and the fact that invalid fields cause no change at all, which directly affects how values should be constructed.

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 (ersätter/skrivs över) and resource (fält i steg 2–6) and explicitly scopes itself against the sibling fill_input, which handles step 1. An agent can distinguish this tool from fill_input and read_draft without opening any schema.

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?

Gives explicit when (steps 2–6, including yes/no questions in steps 3–6) and when-not (step 1 goes to fill_input), and names the sibling tools that handle step 1. It also adds an operational rule: ask the user for unknown data rather than inventing it.

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

All DigitalK2 toolsInspect
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