Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

evidence_register

Binds a scoped report to its current source files for traceable evidence capture, without validating or proving the report's assertions.

Instructions

Read and bind a real scoped report and its current source files. Does not prove its assertions.

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>",
      "report": "<report>"
    },
    "name": "evidence_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportYes
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 description adds one genuinely useful behavioral fact beyond the annotations: it does not validate or prove the assertions in the report, so an agent knows registration is not verification. It does not explain what state is created by registering, whether re-registering is safe, or what the revision check entails, and its 'read' framing sits uneasily with readOnlyHint=false without explanation.

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?

Two tightly written sentences with the action stated first and the key limitation second; no filler. It is arguably too terse, omitting necessary detail rather than wasting words.

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 state-mutating registration tool with two undocumented required parameters and no usage guidance, the description leaves too much unspecified. An agent cannot tell from this text how the report and expected_revision are interpreted or what happens on a revision mismatch.

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?

Both required parameters (report, expected_revision) have zero schema description coverage, and the description supplies almost nothing: 'scoped report' hints at the report argument and 'current source files' gestures at the revision check, but neither is explained. With no coverage in the schema, the description should carry this burden and does not.

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 names a concrete action ('Read and bind a real scoped report and its current source files'), so the resource and rough action are identifiable. However, 'bind' is jargon that leaves the actual effect (registering an evidence record) ambiguous, and no sibling such as evidence_inherit is named to differentiate it.

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 statement of when to use this versus alternatives, no prerequisites, and no exclusions. The clause 'Does not prove its assertions' is a caveat about what the tool does not do, not guidance about when to invoke it.

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