Skip to main content
Glama
Sign In
lattice-mcp

lattice-mcp

by aidenappl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lattice_upgrade_worker

Upgrade a worker runner to the latest version by providing its worker ID.

Instructions

Upgrade worker runner to latest version

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_upgrade_worker"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWorker ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It states 'upgrade' implying mutation, but fails to mention whether it's destructive, if it causes downtime, requires specific permissions, or what happens to running tasks. This opacity is insufficient for safe agent invocation.

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?

The description is a single sentence with no unnecessary words. It is front-loaded and achieves maximum efficiency, earning its place.

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 lack of output schema and annotations, the description should explain return format, error conditions, or side effects. It does none of this, leaving the agent to assume success/failure without details. For a mutation tool, this is incomplete.

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?

The input schema has 100% coverage with one parameter 'id' described as 'Worker ID'. The description adds no additional semantics, such as format or constraints, so baseline 3 is appropriate.

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?

The description 'Upgrade worker runner to latest version' clearly states the verb (upgrade), resource (worker runner), and scope (to latest version). Among sibling tools like lattice_update_worker and lattice_reboot_worker, this tool is uniquely identified by specifying the runner upgrade, so purpose is distinct.

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?

The description provides no guidance on when to use this tool versus alternatives, such as lattice_update_worker or lattice_reboot_worker. There is no mention of prerequisites (e.g., worker must exist) or situations to avoid using it, leaving the agent without decision-making support.

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