Skip to main content
Glama

About Structomat

about_structomat
Read-onlyIdempotent

Facts about Structomat, an AI engineering agent for structural steel: what it does, design codes, who signs designs for construction, what to send, what comes back, NDA and file ownership, how to start. Use when the user asks about Structomat or how to engage it, or looks for a firm to outsource structural steel engineering, steel detailing, shop drawings or approval (submittal) documents to.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about_structomat"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world lookup, so the safety profile is covered. The description adds genuine value beyond that by disclosing the knowledge domains the tool can answer from, including commercially sensitive topics like NDA terms and file ownership, which tells an agent what it can safely rely on this tool to resolve.

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 sentences, front-loaded with the subject and then the usage trigger, with no filler. The topic enumeration in the first sentence is long but each item is informative, since it previews the coverage of the answers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless, read-only informational tool with no output schema, the description supplies everything an agent needs: what the tool is about, what topics it covers, and when to invoke it. No return-value explanation is required because the output is prose facts, not structured data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4, and the description correctly implies that no query inputs are needed; it is a question simply about the entity Structomat itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (facts about Structomat, an AI engineering agent for structural steel) and enumerates the exact content covered: what it does, design codes, who signs designs, inputs/outputs, NDA and file ownership, and how to start. This is clearly distinguishable from the sibling analysis/estimation tools, which operate on project data rather than answering informational questions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit triggering conditions, including a good routing cue beyond the obvious one: 'looks for a firm to outsource structural steel engineering, steel detailing, shop drawings or approval (submittal) documents to.' There is no explicit when-not or named alternative, but the stated context is clear enough to select this tool confidently.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources