Skip to main content
Glama

Gas pipeline design pressure, MAOP and impact radius (49 CFR 192)

pipeline_design_and_maop
Read-onlyIdempotent

Steel gas pipeline arithmetic with citations: class location from building count (192.5), design pressure P = (2St/D) x F x E x T (192.105-192.115), test-pressure factor and MAOP as the lowest limit (192.619(a)), hoop stress as % SMYS, and potential impact radius (192.903).

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": {
      "smys": "<smys>",
      "wall": "<wall>",
      "od": "<od>"
    },
    "name": "pipeline_design_and_maop"
  }
}

Input Schema

NameRequiredDescriptionDefault
odYesOutside diameter, inches
smysYesSpecified minimum yield strength, psi
wallYesNominal wall thickness, inches
gasTempFNoGas temperature, °F
testPsigNoPost-construction test pressure, psig
buildingsNoBuildings intended for human occupancy in the class location unit
installedNoInstall date YYYY-MM-DD
classLocationNoClass location 1-4 (overrides buildings)
historicalPsigNoHighest actual operating pressure in the look-back period

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description does add regulatory grounding by citing the specific sections each calculation follows and by clarifying that MAOP is the lowest of the applicable limits, which is meaningful behavior. It does not disclose what the response contains (per-computation values vs. a single verdict) or how partially supplied inputs degrade the result.

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 that front-loads the core purpose ('Steel gas pipeline arithmetic with citations') and then enumerates each output with its citation. No filler, but the run-on clause structure makes it slightly harder to scan for which inputs unlock which result.

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?

With 9 parameters, no output schema, and multiple distinct computations bundled into one call, the description should indicate which inputs are needed for which result and what the return looks like. It names the calculations but leaves the mapping (e.g., buildings vs. classLocation override, testPsig required for MAOP) entirely to the schema, so an agent can invoke it but may not know which outputs to expect from a partial input set.

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?

Schema description coverage is 100%, so every parameter is already documented, and the baseline of 3 applies. The description adds conceptual linkage by naming the formula variables (S, t, D, F, E, T), the class-location building count, and the test-pressure factor, but it never touches installed, historicalPsig, or gasTempF, so several inputs remain uncontextualized beyond their schema text.

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?

The description names a specific resource (steel gas pipeline arithmetic) and enumerates the exact computations performed: class location, design pressure, test-pressure factor/MAOP, hoop stress as % SMYS, and potential impact radius, each tied to a CFR section. This is far more informative than a name restatement. It stops short of explicitly distinguishing itself from the CFR-lookup siblings (cfr_lookup, cfr_search), leaving the agent to infer that this tool computes rather than retrieves.

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 implied by the enumeration of computations: an agent can infer it should call this when it needs a design-pressure or MAOP number rather than a regulation text. However, there is no explicit when-to-use statement, no guidance on choosing this over cfr_lookup for the cited sections, and no note on prerequisites such as needing testPsig before MAOP can be reported.

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.