Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

stage_advance

Destructive

Advance an architectural modeling workflow to the next stage only when evidence and design decision conditions are met, using target, expected revision, and reason.

Instructions

Advance one stage only after evidence and design decision conditions are met.

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": {
      "expected_revision": "<expected_revision>",
      "target": "<target>",
      "reason": "<reason>"
    },
    "name": "stage_advance"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
targetYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

The gating prerequisite adds real behavioral context beyond the annotations, which already declare a destructive, non-idempotent write. Still missing: what state is destroyed or overwritten by the advance, what happens when expected_revision does not match, and whether the advance is reversible (stage_reopen exists but is not mentioned).

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?

A single front-loaded sentence with no wasted wording. It is tight, though the brevity arguably comes at the cost of the missing detail noted elsewhere rather than from disciplined editing.

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?

The output schema removes any need to describe return values, which helps. But for a destructive, non-idempotent mutation with three undocumented required parameters, the description leaves out too much about preconditions, revision semantics, and recovery.

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?

All three required parameters have 0% schema description coverage, and the description explains none of them. It never clarifies what expected_revision is for (optimistic concurrency), what target selects, or what reason is used for, so an agent must guess at invocation semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'advance' and resource 'stage' are identifiable, and 'one stage only' hints at differentiation from stage_reopen. However, the domain term 'stage' and what advancing it means in the workflow are never explained, and the relationship between 'advance one stage' and the target enum (selection/development/refinement/handoff) is left ambiguous.

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?

It states a precondition ('only after evidence and design decision conditions are met'), which is useful when-to-use context. It does not say how to verify those conditions (e.g., via stage_check) or what to do instead when they are not met, so routing guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.