Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Continue Accounting Workflow

continue_accounting_workflow
Idempotent

Advance an ongoing accounting workflow by answering its current question, resolving a review item, or preparing an approval action for execution.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNonext reads workflow_state_json; resolve_review/prepare_action read review_item_json; execute_review_action books a prepared owner-expense continuation with plan_handle.
answerNoFree-text answer to the current workflow question, for a compact guided continuation. Capped so a whole continuation stays within the 1 KiB budget.
item_idNoStable id of the workflow item this continuation answers (from a workflow_action_v2 blocker or page item).
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 workflow response; required for action='next'.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+}
  2. First observedv0.18.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description states actions like 'resolve' and 'prepare' which imply mutation but not destruction. No contradiction exists, but the description adds little behavioral context beyond what annotations already provide, such as side effects or prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is a single concise sentence that front-loads key actions, with no unnecessary words. It earns its place by being direct and informative.

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?

The tool has 9 parameters, no required params, no output schema, and involves complex workflows. The description alone is insufficient; it does not summarize usage patterns, return values, or prerequisites. The agent must rely heavily on schema descriptions, which are detailed but not a substitute for a complete description.

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%, with each parameter having a detailed description (e.g., action enum, plan_handle format). The main description is brief and does not add meaning beyond the schema, but the schema itself is informative. Baseline 3 is appropriate.

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?

The description explicitly states the tool's purpose: 'Continue an accounting workflow response, resolve a review item, or prepare an approval action.' It uses specific verbs and resources, clearly distinguishing it from sibling tools (e.g., invoices, clients).

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

Usage Guidelines3/5

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

The description does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. However, the sibling tools are largely unrelated (CRUD operations), so the agent can infer the tool's specialized role. The enum descriptions in the schema offer some context for each action.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iseppo/e-arveldaja-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server