Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Continue Accounting Workflow

continue_accounting_workflow
Idempotent

Advance an accounting workflow, resolve review items, or prepare and execute 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. Changed1 schema field changedv0.29.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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."
  3. 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"
+}
  4. First observedv0.18.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the description is not the sole safety source. But it adds nothing beyond them: it does not disclose that execute_review_action actually books an owner-expense continuation, nor clarify what 'prepare' versus 'execute' destroy or commit. The one self-describing phrase, 'prepare an approval action', understates the mutating execute action.

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?

A single front-loaded sentence with no padding. It is efficiently sized, though the terseness is part of the completeness gap rather than pure virtue.

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

Completeness2/5

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

For a complex, mutation-capable tool spanning four actions and eight parameters with no output schema, the description is far too thin. It never explains the workflow-handle/plan-handle lifecycle, the consume-once plan_handle semantics, or the difference between preparing and executing, leaving the detailed schema to carry the entire burden.

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 schema fully documents the eight parameters, including the action enum and each action's required handle. The description adds no parameter syntax, formats, or inter-parameter dependencies. Per the high-coverage baseline, a 3 is appropriate.

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

Purpose3/5

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

The description names three sub-actions (continue a workflow response, resolve a review item, prepare an approval action) which clarifies the multi-action nature beyond the bare title. However, it omits the fourth supported action (execute_review_action, which books a prepared continuation), and it does not distinguish this tool from any sibling. It is specific enough to be usable but incomplete.

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?

It lists what the tool can do but gives no when-to-use guidance: no mention of prerequisites such as needing a workflow_handle, review_item_json, or the plan_handle required by execute_review_action, and no routing against siblings like recommend_workflow or get_operation_result_page. The agent must infer all triggering conditions from the schema.

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