Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

stage_reopen

Destructive

Return to an earlier modeling stage to revise decisions while preserving existing facts and prior evidence.

Instructions

Return to an affected earlier stage without erasing facts or old evidence.

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

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

C2.7/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds useful context that facts and old evidence are preserved, which partially clarifies the destructive scope. It does not explain what is actually destructive, whether later stages are invalidated, or what permissions or side effects apply.

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 single sentence is front-loaded and free of filler. It is perhaps over-compressed: "affected earlier stage" is the only qualifier and remains ambiguous.

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 destructive workflow mutation with three required parameters and no parameter documentation, the description is too sparse. It omits usage guidance, parameter semantics, and side-effect disclosure; the existing output schema covers return values, but the input and behavioral picture remain incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With three required parameters and 0% schema description coverage, the description must compensate but mentions none of them. It gives no meaning for target, expected_revision, or reason, leaving the agent to infer enum semantics and concurrency behavior entirely from bare field names.

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?

The description uses a specific verb ("Return") and resource ("earlier stage"), making the core action clear. However, "affected earlier stage" is somewhat vague, and it does not distinguish this tool from siblings like stage_advance or stage_check.

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?

It provides no explicit when-to-use guidance, no prerequisites, and no alternatives. The phrase "without erasing facts or old evidence" is a behavioral reassurance, not a usage condition, so an agent must infer when reopening rather than advancing or checking a stage is appropriate.

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