Skip to main content
Glama
Sign In
@millwork/solver-mcp

@millwork/solver-mcp

Official
by millworkdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

solver_status

Retrieve the current lifecycle state of an execution using its execution ID to track progress and determine whether it is pending, running, or completed.

Instructions

Poll an execution's lifecycle state (GET /v1/executions/{id}).

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": {
      "execution_id": "<execution_id>"
    },
    "name": "solver_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
execution_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that this is a GET polling operation, which indicates a read-only style behavior. It does not, however, describe whether the poll blocks, what lifecycle states exist, or what error responses look like.

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, front-loaded sentence that states the action, resource, and endpoint with no filler or redundancy. Every word earns its place.

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 one-parameter status-polling tool, the core call semantics are covered. However, with no output schema and no annotations, the description omits what the response looks like, what lifecycle values are possible, and how the agent should interpret the result, leaving the tool partially underspecified.

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 description maps the sole execution_id parameter to the {id} path segment in GET /v1/executions/{id}, which adds mild clarity beyond the bare schema. Still, it does not explain the expected format, source, or validation behavior of execution_id, leaving some room for interpretation.

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 uses a specific verb ('Poll') and a clear resource ('an execution's lifecycle state'), and it pins the operation to an exact HTTP endpoint. This makes the tool's purpose immediately identifiable and distinct from sibling tools like solver_result or solver_submit.

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 phrasing implies this tool is for checking an execution's lifecycle state after submission. However, it does not explicitly state when to prefer this over similar siblings such as solver_result or solver_poll_source_handoff, nor does it mention any exclusions or polling frequency.

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