Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

disable_plan

Disables a backup plan to stop its events from running. Requires confirm:true; otherwise returns the command only.

Instructions

Disables a backup plan so its events no longer run. Requires confirm:true; without it only the command that WOULD run is returned.

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": {
      "id": "<id>"
    },
    "name": "disable_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlan id
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 disclose two key traits: the state change (events stop running) and the confirm-gated preview path. It leaves out reversibility (that enable_plan can undo it), permission requirements, and behavior for an already-disabled or unknown plan id.

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?

Two short sentences, front-loaded with the effect and then the invocation requirement. Every clause earns its place and nothing is padded.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the essential state change and the confirm gate. The main residual gap is what the preview response looks like and what happens on invalid or already-disabled plans.

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%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining what happens when confirm is absent — the would-run command is returned rather than executed. That clarifies the practical semantics of the confirm flag beyond its terse schema note.

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?

States a specific verb and resource ("Disables a backup plan") plus the concrete effect ("so its events no longer run"), which an agent can act on directly. It does not explicitly name the counterpart enable_plan, so sibling differentiation is implied rather than stated.

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?

Gives a clear operational condition: confirm:true is required to actually disable, otherwise a preview of the command is returned. That effectively documents a dry-run mode. It does not discuss when to disable versus delete_plan or task_disable, but the invocation guidance is unambiguous.

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