Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

handoff_export

Freeze a stage-approved handoff by exporting source hashes, actual geometry, and explicit unverified scope to a destination for traceable project transfers.

Instructions

Freeze a stage-approved handoff with source hashes, actual geometry and explicit unverified scope.

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": {
      "destination": "<destination>",
      "geometry_path": "<geometry_path>",
      "model_paths": "<model_paths>"
    },
    "name": "handoff_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationYes
model_pathsYes
geometry_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds real context beyond that: the output is a frozen snapshot that records source hashes and 'explicit unverified scope', which tells the agent the result is an immutable record with declared gaps. It stops short of saying whether an existing destination is overwritten, what permissions are required, or whether repeated calls create new artifacts.

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, and the frozen-artifact nature is prioritized first. It is dense to the point of opacity ('explicit unverified scope') but every clause carries meaning rather than padding.

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 explained, and the annotations cover the safety profile. However, for a three-required-parameter export tool with zero schema descriptions, the definition leaves the entry conditions and the semantics of destination and model_paths underspecified.

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% for three required parameters, so the description carries the full burden. It only loosely gestures at them via 'actual geometry' and 'source hashes'; it never clarifies whether destination is a file path or directory, what form model_paths must take, or how geometry_path relates to model_paths, and one parameter (destination) receives no coverage at all.

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?

States a specific verb and resource: 'Freeze a stage-approved handoff', and enumerates what the artifact captures (source hashes, actual geometry, unverified scope). That is far more than a restatement of the name, but the phrasing is domain jargon and never names the adjacent export tool so an agent must infer the boundary from the sibling list.

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 or when-not-to-use statement, and no alternative is named. The modifier 'stage-approved' hints at a precondition but never says what approval means or what to do if a stage is not approved, leaving the agent to guess at the trigger condition.

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