Skip to main content
Glama

status

Transitions a component's build lifecycle state after pre-commit gates and delta/seam tests pass, recording readiness, QA, verified, failed, or stale outcomes.

Instructions

Step 4 (Transition Status): Transition a component's build lifecycle status (e.g. new_status='VERIFIED' after pre-commit gate and delta/seam tests pass).

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": {
      "component": "<component>",
      "new_status": "<new_status>"
    },
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardNoTarget board name (default: lattice_core)
reasonNoOptional failure diagnostic
core_tagNoOptional core tag
build_tagNoOptional build tag
componentYesComponent scope ID
new_statusYesTarget status (READY, IN_PROGRESS, IN_QA, VERIFIED, FAILED, STALE)
project_rootNoOptional repository root path (auto-discovered by board name or file paths if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 disclose mutation behavior. It implies a state-changing transition and mentions a gating condition for VERIFIED, but omits required permissions, reversibility, side effects, failure behavior, and what other statuses mean operationally.

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?

Single front-loaded sentence with a parenthetical workflow label and one inline example; no redundant wording. It is concise, though the brevity contributes to the behavioral gaps scored elsewhere.

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?

For a mutation tool with no annotations and no output schema, the description is thin: it covers the core transition and one status condition but not permissions, side effects, return behavior, or the semantics of other statuses and parameters. Schema coverage helps, but the description leaves important call-context gaps.

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%, so the schema already documents all seven parameters. The description adds only the example new_status='VERIFIED' and the gate condition, without explaining component scope, reason, tags, or project_root beyond the schema.

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?

Explicitly states the action: transition a component's build lifecycle status, and frames it as Step 4 of a workflow with a concrete example. It does not differentiate from sibling tools, but none of the listed siblings appear to share this purpose.

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 description implies the tool is used as a workflow step and gives one condition for setting VERIFIED after gates/tests pass. It provides no guidance for other statuses or when not to use it, and names no alternative tool.

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