Skip to main content
Glama

backend_control

Start, stop, or check an add-on's runtime, including its VM for ise_spartan3; stopping frees RAM and is refused while a build runs.

Instructions

Start, stop or check an add-on's runtime (for ise_spartan3: its VM).

action: 'start', 'stop' or 'status'. Stopping frees RAM; it is refused while a build runs.

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": {
      "backend": "<backend>",
      "action": "<action>"
    },
    "name": "backend_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
backendYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add real behavioral context: stopping frees RAM and is rejected during a running build. It omits what 'status' returns, whether start is idempotent, and what happens on an already-stopped backend.

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 operation, followed immediately by the action enumeration and the one non-obvious constraint. No filler or redundancy.

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 a two-parameter, no-annotation, no-output-schema tool this is close, since the action values and the main side effect are covered. The missing piece is backend identification — no examples, no hint that list_backends supplies valid names — which is the likeliest source of a failed call.

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 0% and neither parameter has a title beyond 'Action'/'Backend'. The description compensates for the action parameter by naming the three valid values ('start', 'stop' or 'status'), which the schema lacks via an enum. It adds nothing about the 'backend' parameter — no example values or pointer to list_backends — leaving half the surface undocumented.

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 opens with a specific verb set and resource: 'Start, stop or check an add-on's runtime'. It also clarifies the resource for the concrete case ('for ise_spartan3: its VM'), which makes the object of the operation unambiguous. It does not explicitly contrast with siblings such as build_status, so it stops short of a 5.

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?

Usage is implied by the action list and one precondition is stated ('refused while a build runs'), which is genuinely useful for sequencing against the build tool. However, there is no explicit statement of when to pick this over build_status or activity, nor guidance on valid backend values; the agent must infer coordination from the sibling list.

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