Skip to main content
Glama

Creep Risk Flag

creep_flag
Read-only

Screens creep risk by comparing operating temperature against a material's maximum service temperature, returning margin, stress, pass/fail, and reason.

Instructions

Screen for creep risk: compare operating temperature to the material's max service temperature (Materials DB, or an override). A screen, not a Larson-Miller life model. pass = below the service limit. Returns {operating_temp_c, service_temp_c, margin_c, stress_mpa, creep_risk, pass, reason}.

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": {
      "stress_mpa": "<stress_mpa>",
      "temp_c": "<temp_c>"
    },
    "name": "creep_flag"
  }
}

Input Schema

NameRequiredDescriptionDefault
temp_cYes
materialNoSteel-1045
workspaceNoRun this call in this named workspace
stress_mpaYes
max_service_temp_cNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), so the description's added value is the decision rule ('pass = below the service limit') and the data provenance (Materials DB or an override). It also discloses the returned field set, which matters because no output schema exists. It does not say what happens on a missing material or how close-to-limit margins are graded.

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?

Front-loaded with the core action and its scope caveat, then the decision rule, then the return shape — no filler sentences. The inline field enumeration is slightly list-like but justified by the absence of an output schema.

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?

For a read-only screening tool with no output schema, the description supplies the pass criterion, the temperature source (DB vs. override), and the return fields — enough to call it correctly. Remaining gaps (material-not-found behavior, how stress enters the check, units) are minor for a screen.

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 coverage is only 20%, so the description must carry the load: it clarifies that temp_c is the operating temperature and that max_service_temp_c is sourced from the Materials DB or supplied as an override. It leaves stress_mpa (a required parameter, and physically central to creep) and workspace unexplained, so roughly half the parameter meaning is still missing.

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+resource (screen for creep risk) and the exact comparison it performs: operating temperature vs. the material's max service temperature. It also explicitly bounds its own scope — 'A screen, not a Larson-Miller life model' — so an agent can distinguish it from a full life-prediction path.

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?

Clear about the context in which it is appropriate (quick screening) and where its answers stop being authoritative ('not a Larson-Miller life model'), which is the key exclusion for creep work. It doesn't name a specific sibling alternative to escalate to, so it falls short of a full 5.

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

Deploy Server

Other Tools