Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

stage_check

Read-onlyIdempotent

Lists stage conditions, stale evidence, and required user decisions for a target stage, so you can confirm readiness before advancing an architectural modeling workflow.

Instructions

List stage conditions, stale evidence and required user decisions.

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": {
      "target": "<target>"
    },
    "name": "stage_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered without the description. The description does add value by naming what is surfaced (stale evidence, pending decisions), which tells the agent the response is diagnostic rather than a simple state dump.

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 short sentence with no filler, and the most useful content (stale evidence, required decisions) is front-loaded. It is under-specified rather than bloated, so length is not the problem.

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?

An output schema exists, so return values need not be described, and annotations cover safety. What is missing is any linkage between the required 'target' argument and the reported conditions, which is the main thing an agent needs before calling this.

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?

Schema description coverage is 0%, and the description never mentions the single 'target' parameter or that it selects one of five lifecycle stages. The enum values are self-explanatory, which prevents a 1, but the description makes no attempt to explain whether target scopes the returned conditions or controls validation.

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 description gives a verb (list) and three things returned (stage conditions, stale evidence, required user decisions), which is more specific than a restatement of the name. However, 'stage conditions' is undefined jargon, and it never says this is the read-only counterpart to stage_advance/stage_reopen, so the agent must infer the distinction from the name alone.

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?

There is no explicit when-to-use guidance and no named alternative. The phrase 'required user decisions' hints this is a pre-advance gate check, but the agent is left to infer that stage_advance is the write-side sibling and that this should be called first.

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