Skip to main content
Glama
Sign In
lattice-mcp

lattice-mcp

by aidenappl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lattice_restart_container

Restart a container by providing its ID to resolve issues or apply updates.

Instructions

Restart a container

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": "lattice_restart_container"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContainer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose whether the restart is graceful, if there is downtime, or what state the container ends up in. For a mutation tool, this is a significant gap.

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 description is very concise (4 words) with no unnecessary words. However, it could be slightly more informative without losing conciseness.

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?

Given the tool's simplicity (1 param, no output schema), the description is too minimal. It does not explain the behavior of restart (e.g., if it stops then starts), prerequisites, or any side effects. The sibling set includes many container lifecycle tools, making this lack of detail more problematic.

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% with one parameter 'id' described as 'Container ID'. The description adds no additional meaning beyond the schema, so baseline of 3 is appropriate.

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?

Description clearly states the action (restart) and resource (container). It is straightforward, but does not differentiate from similar tools like stop, start, kill, pause, unpause, remove, recreate, etc.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like lattice_stop_container, lattice_start_container, lattice_recreate_container, or lattice_restart_stack. There is no explicit when-to-use or when-not-to-use information.

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