Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

evidence_inherit

Destructive

Reuse prior check evidence only when declared dependencies and semantic basis remain unchanged; do not infer missing dependencies.

Instructions

Inherit only a check whose declared dependencies are actually unchanged and semantic basis is unchanged. Missing dependencies cannot be guessed.

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": {
      "old_report_path": "<old_report_path>",
      "before_geometry_path": "<before_geometry_path>",
      "after_geometry_path": "<after_geometry_path>",
      "report_path": "<report_path>"
    },
    "name": "evidence_inherit"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_pathYes
old_report_pathYes
after_geometry_pathYes
before_geometry_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the agent knows this mutates state. The description adds the dependency-validation rule but never discloses what is written or overwritten at report_path, whether an existing report is replaced, or what happens when inheritance is refused beyond 'cannot be guessed'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, so there is no waste, but the text is terse to the point of obscurity and leads with a conditional clause rather than stating the action. Brevity here costs clarity rather than buying it.

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?

This is a four-required-parameter, destructive, non-idempotent operation with zero schema descriptions; an output schema exists so return values need not be explained. Even so, the description leaves the agent without the meaning of three of the four paths or any warning about overwriting report_path, which is far short of sufficient for the complexity.

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% and all four parameters (old_report_path, before_geometry_path, after_geometry_path, report_path) carry only generic titles. The description mentions 'declared dependencies' and 'semantic basis' without mapping them to the before/after geometry paths or explaining the old-vs-new report relationship, so it compensates for essentially none of the coverage gap.

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 'inherit' and the object 'a check' are present, and the qualifier 'whose declared dependencies are actually unchanged' narrows the intent, but the description never states operationally what inheriting produces (e.g., carrying a check result from old_report_path into report_path). An agent can guess the general area but not the concrete effect.

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?

'Inherit only a check whose declared dependencies are actually unchanged and semantic basis is unchanged' gives a positive precondition, and 'Missing dependencies cannot be guessed' states a negative one. However, no alternatives are named (evidence_register exists as a sibling), and the guidance is stated as a rule rather than as when to pick this tool over re-running a check.

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