Skip to main content
Glama
Sign In

Piping Toolset Engineering Data

by com.pipingtoolset
OverviewDiscussionsAdmin

AISC shape properties

get_aisc_shape
Read-onlyIdempotent

Return the dimensions and section properties of one AISC shape by designation (e.g. W8X31, HSS6X6X3/8, PIPE4STD, L4X4X1/2): weight, area, depth, flange and web dimensions, I, S, Z, r, J and Cw as applicable. Source: AISC Shapes Database v16.0; L, HSS and Pipe computed from nominal geometry.

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

Input Schema

NameRequiredDescriptionDefault
designationYesAISC designation, spaces ignored, e.g. W8X31

Output Schema

NameRequiredDescriptionDefault
familyYes
sourceYes
propertiesYes
attributionYes
designationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds real value beyond that by naming the data source (AISC Shapes Database v16.0) and warning that L, HSS and Pipe values are computed from nominal geometry rather than taken straight from the database. It stops short of stating error behavior for invalid designations or the unit system, which are the remaining behavioral unknowns.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and input format, then the returned fields, then provenance. No filler and nothing repeated from the schema verbatim.

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

Completeness4/5

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

With an output schema present, the description need not document return values, and it is already complete on input format and data provenance. The one notable omission is the unit convention (imperial, per AISC v16) and the behavior for an unrecognized designation, which an agent would want before calling.

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

Parameters3/5

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

The single parameter is already fully documented in the schema, including the 'spaces ignored' rule, so the baseline is a 3. The description does add modest value by showing designation formats across four shape families (W, HSS, PIPE, L), which exceeds the schema's single W8X31 example and helps an agent construct valid input.

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?

A specific verb and resource ('Return the dimensions and section properties of one AISC shape') plus concrete designation examples (W8X31, HSS6X6X3/8, PIPE4STD, L4X4X1/2) and an enumerated property list. It does not, however, differentiate itself from the sibling get_pipe_dimensions even though it explicitly accepts PIPE designations, leaving a small overlap an agent must resolve itself.

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?

Usage is only implied: an agent can infer 'supply a designation, get properties back', but there is no explicit when-to-use statement, no exclusion of the pipe-specific sibling, and no guidance on what to do when a designation is unknown.

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

All Piping Toolset Engineering Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources