Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

project_init

Create a project record with name, brief, stage, and entry evidence for architectural modeling workflows while preserving existing projects from overwrite.

Instructions

Create one current fact record; existing projects are never overwritten.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
briefNo
stageNoexploration
entry_evidenceNo

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false; the description adds a consistent and valuable behavioral guarantee that existing records are never clobbered. The big remaining gap is duplicate handling: with idempotentHint=false and a non-overwrite rule, an agent cannot tell whether a repeat init fails, returns the existing record, or creates a conflicting entry.

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 filler or redundancy. It is efficiently written, though its brevity reflects under-specification rather than disciplined economy, which keeps it out of the top band.

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?

An output schema exists, so return values need not be described, but for a mutation tool with a required name, an enum-typed stage, an evidence field, and zero schema coverage, the description omits nearly everything an agent needs to invoke it correctly. The duplicate/existing-project behavior in particular should be spelled out.

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?

Schema description coverage is 0% across four parameters, and the description compensates for none of them: no mention of name, brief, the five-value stage enum, or entry_evidence. The only hint is that some record is created, which gives no meaning to any individual parameter, so the agent must guess from bare titles.

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 states a create action ("Create one current fact record") and a non-overwrite guarantee, but the resource phrasing is odd: it never says "project" even though the tool name and siblings imply it, and "current fact record" is unexplained jargon. An agent can infer it initializes a record, but the verb+resource pairing is weaker than a sibling like project_get or project_update.

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?

"Existing projects are never overwritten" implicitly routes an agent toward project_update when a project already exists, which is useful implied usage. However, it never explicitly says when to use this versus project_get or project_update, nor what to do if the project exists (error? no-op?), so guidance remains inferred rather than stated.

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