Piping Toolset Engineering Data

Pipe OD and wall by schedule

get_pipe_dimensions

Read-onlyIdempotent

Return the outside diameter and nominal wall thickness (in) for a nominal pipe size per ASME B36.10M / B36.19M: one schedule with its wall and inside diameter when schedule is given (e.g. 40, STD, XS, 80, 10S), otherwise the walls of every schedule listed at that size.

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": {
      "nps": "<nps>"
    },
    "name": "get_pipe_dimensions"
  }
}

Input Schema

Name	Required	Description	Default
`nps`	Yes	Nominal pipe size, e.g. 6, 1-1/2, 3/4
`schedule`	No	Schedule or weight class, e.g. 40, STD, XS, 160, 10S

Output Schema

Name	Required	Description	Default
`od`	Yes
`nps`	Yes
`mode`	Yes
`unit`	Yes
`walls`	Yes
`notice`	Yes
`citation`	Yes
`schedule`	Yes
`verify_at`	Yes
`tier_required`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: units, the governing standard, and the asymmetric return shape (inside diameter only in the single-schedule case). It does not disclose failure behavior for invalid inputs.

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 dense sentence, front-loaded with what is returned, followed by the conditional behavior. No filler, though the trailing colon clause packing both modes into one sentence is slightly tangled and could be split for faster scanning.

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 needn't document return fields, and it nonetheless clarifies units and the branching return shape. Annotations handle the safety profile. The only gap is validation/error behavior for unknown NPS or schedule values.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the examples confirm `schedule` accepts both numeric schedules and weight classes (STD, XS, 10S), and it explains the consequence of omitting the optional parameter. It does not add format rules for `nps` beyond the schema's own examples.

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?

States a specific verb and resource (return outside diameter and nominal wall thickness for a nominal pipe size), names the governing standards ASME B36.10M / B36.19M, and gives units in inches. The title and description together make it unambiguous against unrelated siblings such as get_aisc_shape or the dataset/key tools.

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?

The description explicitly defines the two calling modes: pass `schedule` to get one schedule's wall and inside diameter, omit it to get every schedule at that size. That is clear operational context, but it offers no exclusions or error guidance (e.g. what happens with an unrecognized schedule or NPS).

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 tools Inspect

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.