Skip to main content
Glama
Sign In
capsule-agents

capsule-agents

by bingqing007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

capsule_run

Run isolated main and sub-agent tasks in networkless Docker with explicit text inputs, a host-configured Ollama model, verified artifact delivery, and reviewer oversight.

Instructions

Run an isolated main/sub-agent team on explicit task and text copies. Requires Docker and a host-configured Ollama model.

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": {
      "task": "<task>"
    },
    "name": "capsule_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
inputsNoExplicit text copies keyed by flat filenames; never host paths.
timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds the real-world prerequisite context (Docker + host-configured Ollama model) and the 'isolated' execution claim, but never explains side effects, whether runs can be repeated safely, or what a failed prerequisite yields.

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?

Two tight sentences with the action front-loaded and the constraint immediately after; no filler. It is arguably under-specified rather than bloated, but nothing is wasted.

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?

With no output schema, three parameters (one a nested map), and an execution tool that mutates state, the description covers the concept and prerequisites but omits what gets produced, failure behavior, and how timeout interacts with long-running agent teams. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: 'task' and 'timeout' have no schema descriptions, and the 'inputs' description ('flat filenames; never host paths') is already in the schema. The description's phrase 'explicit task and text copies' maps loosely to task/inputs but adds no format, size, or timeout guidance to compensate for the gap.

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 ('Run') and resource (an isolated main/sub-agent team) acting on a task plus text copies — far more than a restatement of the name. It does not, however, distinguish itself from capsule_demo or capsule_doctor, so an agent has to infer which 'capsule_' variant to pick.

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 prerequisite ('Requires Docker and a host-configured Ollama model') gives useful context for when this call can succeed. There is no guidance on when to choose capsule_run over capsule_demo/capsule_doctor, no exclusions, and no statement of what happens when the prerequisites are absent.

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