Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Continue Accounting Workflow

continue_accounting_workflow
Idempotent

Continue accounting workflows by advancing to the next step, resolving review items, or preparing approval actions.

Instructions

Continue an accounting workflow response, resolve a review item, or prepare an approval action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNonext reads workflow_handle (+ item_id) or workflow_state_json; resolve_review/prepare_action read review_item_json; execute_review_action books a prepared owner-expense continuation with plan_handle.
item_idNoStable id of a workflow item (from a workflow_action_v2 blocker or page item); action='next' returns the item after it.
plan_handleNoFor action='execute_review_action': the consume-once plan handle minted by action='prepare_action' for a server-executed owner-expense continuation. Drift-bound to the reviewed booking params; not itself approval.
save_as_ruleNoFor action='prepare_action', prepare save_auto_booking_rule when appropriate.
workflow_handleNoOpaque server-issued workflow handle from a compact workflow_action_v2 response. Carries inert prior workflow state; never approval or mutation authority.
review_item_jsonNoReview item object for action='resolve_review' or action='prepare_action'.
rule_override_jsonNoOptional explicit rule fields for action='prepare_action'.
workflow_state_jsonNoPrevious v1 workflow response; required for action='next' without workflow_handle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.27.0
    • changedInput schema / properties / action / description
      Previous value: -"next reads workflow_state_json; resolve_review/prepare_action read review_item_json; execute_review_action books a prepared owner-expense continuation with plan_handle."New value: +"next reads workflow_handle (+ item_id) or workflow_state_json; resolve_review/prepare_action read review_item_json; execute_review_action books a prepared owner-expense continuation with plan_handle."
    • removedInput schema / properties / answer
      Removed value: -{
-  "description": "Free-text answer to the current workflow question, for a compact guided continuation. Capped so a whole continuation stays within the 1 KiB budget.",
-  "maxLength": 700,
-  "type": "string"
-}
    • changedInput schema / properties / item_id / description
      Previous value: -"Stable id of the workflow item this continuation answers (from a workflow_action_v2 blocker or page item)."New value: +"Stable id of a workflow item (from a workflow_action_v2 blocker or page item); action='next' returns the item after it."
    • changedInput schema / properties / workflow_state_json / description
      Previous value: -"Previous workflow response; required for action='next'."New value: +"Previous v1 workflow response; required for action='next' without workflow_handle."
  2. Changed6 schema fields changedv0.25.2
    • changedInput schema / properties / action / description
      Previous value: -"next reads workflow_state_json; resolve_review/prepare_action read review_item_json."New value: +"next reads workflow_state_json; resolve_review/prepare_action read review_item_json; execute_review_action books a prepared owner-expense continuation with plan_handle."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "next",
-  "resolve_review",
-  "prepare_action"
-]New value: +[
+  "next",
+  "resolve_review",
+  "prepare_action",
+  "execute_review_action"
+]
    • addedInput schema / properties / answer
      Added value: +{
+  "description": "Free-text answer to the current workflow question, for a compact guided continuation. Capped so a whole continuation stays within the 1 KiB budget.",
+  "maxLength": 700,
+  "type": "string"
+}
    • addedInput schema / properties / item_id
      Added value: +{
+  "description": "Stable id of the workflow item this continuation answers (from a workflow_action_v2 blocker or page item).",
+  "maxLength": 128,
+  "type": "string"
+}
    • addedInput schema / properties / plan_handle
      Added value: +{
+  "description": "For action='execute_review_action': the consume-once plan handle minted by action='prepare_action' for a server-executed owner-expense continuation. Drift-bound to the reviewed booking params; not itself approval.",
+  "pattern": "^[A-Za-z0-9_-]{43}$",
+  "type": "string"
+}
    • addedInput schema / properties / workflow_handle
      Added value: +{
+  "description": "Opaque server-issued workflow handle from a compact workflow_action_v2 response. Carries inert prior workflow state; never approval or mutation authority.",
+  "pattern": "^[A-Za-z0-9_-]{43}$",
+  "type": "string"
+}
  3. First observedv0.18.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and readOnlyHint=false, covering retry-safety and mutation potential, so the risk burden is lower. The description itself adds no behavioral context, but the schema's parameter notes supply important traits such as 'consume-once plan handle' and 'never approval or mutation authority', leaving the overall definition non-misleading.

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?

The description is a single tight sentence with no filler, repetition, or unnecessary words. It is concise and front-loaded with the primary continuation capability, though it omits the execute action, which slightly reduces completeness for a complex tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, 4-action tool with no output schema, the description alone is not sufficient: it leaves out execute_review_action and does not explain how actions relate to parameters. The input schema and annotations fill most of the gaps, making the full definition workable, but the description does not stand alone.

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 100%, so the baseline is 3, and the tool description adds no parameter-level meaning. The schema descriptions are detailed about which actions read which parameters, so there is no semantic gap, but the description field provides no additional value here.

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 description states three distinguishable operations: continue a workflow, resolve a review item, and prepare an approval action, using explicit verbs and resources that go beyond the title. However, the phrasing 'continue an accounting workflow response' is awkward, and the description omits the 'execute_review_action' capability that is present in the schema, so it does not fully map to the action enum.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus siblings such as recommend_workflow, accounting_inbox, or save_auto_booking_rule, and it offers no exclusions or prerequisites. The schema's action descriptions imply usage per action, but the tool description itself does not help an agent decide between this and alternative tools.

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

Deploy Server

Other Tools