Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

run_tasks_once

Back up chosen tasks from a plan once without running the whole plan. Creates a temporary plan for the task subset and returns its plan ID and job ID; requires confirm:true.

Instructions

Backs up chosen tasks of a plan once, without running the whole plan. P5 cannot submit a task subset, so a temporary plan 'mcp-once-' with copies of those tasks and one event into the pool is created and started; returns the temp plan id and job id. The temp plan is kept until run_tasks_once_cleanup is called after the job finished. Requires confirm:true.

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": {
      "plan": "<plan>",
      "tasks": "<tasks>"
    },
    "name": "run_tasks_once"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesSource plan id
poolNoPool (default: pool of the plan's first event)
levelNoBackup level (default full)
tasksYesTask ids of that plan
confirmNoMust be true to actually run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the internal temp plan named 'mcp-once-<timestamp>', that copies of tasks plus one event go into the pool, that the plan is created and started, what ids are returned, and that cleanup is required afterward. It omits permission/auth requirements and any side effects on the source plan, keeping it below 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.

Conciseness4/5

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

The core action and scope are front-loaded in the first sentence, followed by the mechanism and the cleanup contract. The P5 implementation rationale is slightly tangential but justifies the temp-plan behavior an agent will observe.

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 a 5-parameter mutation tool with no annotations and no output schema, the description covers the mechanism, required confirmation, returned ids and lifecycle sufficiently to invoke it correctly. Auth/permission preconditions are the main missing element.

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 coverage is 100%, so the schema already documents plan, pool, level, tasks and confirm. The description reinforces the confirm:true gate and the task-subset semantics but adds no syntax or format detail beyond what the schema provides, making the baseline 3 correct.

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 and resource — back up a chosen subset of a plan's tasks exactly once — and immediately contrasts it with running the whole plan. An agent can distinguish it from dryrun_plan or container_backup 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 Guidelines4/5

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

Implies the selection condition (partial subset, single run, not a full plan execution) and explicitly routes the agent to run_tasks_once_cleanup once the job finishes. It does not name an explicit when-not or compare against dryrun_plan, so a small gap remains.

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