Skip to main content
Glama

FEM Thermal Results

fem_thermal_results
Read-only

Extract min, max, and mean temperatures plus top N hottest nodes from a completed thermal run by passing an analysis or job ID.

Instructions

Extract temperature field summary from a completed thermal run. Pass analysis, or the job_id of a finished fem_run_submit solve. Returns {temperatures_c: {min, max, mean}, top_n_hot_nodes: [...]}.

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": "fem_thermal_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNo
job_idNo
analysisNo
workspaceNoRun this call in this named workspace

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. Changed5 schema fields changedv0.5.5
    • addedInput schema / properties / analysis / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / analysis / default
      Added value: +null
    • removedInput schema / properties / analysis / type
      Removed value: -"string"
    • addedInput schema / properties / job_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Job Id"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "analysis"
      -]
  3. 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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the return payload shape ({temperatures_c, top_n_hot_nodes}), useful because no output schema exists, but says nothing about behavior on an unfinished/failed run or on ambiguous job_id/analysis.

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?

Three short sentences, front-loaded with the action, and every line carries information the agent needs — input routing or output shape. No filler.

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 4-param read tool with no output schema, the description supplies the critical missing pieces: the return structure and the two ways to identify the run. Remaining gaps (meaning of `top_n`, how to obtain an `analysis` identifier) are minor but real.

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 25% (only `workspace` is documented), so the description has to compensate. It does clarify the either/or relationship between `job_id` and `analysis`, but `top_n` is never explained directly (only inferable from top_n_hot_nodes), `analysis` format is undocumented, and `workspace` is left to the schema.

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?

States a specific verb and resource: extract temperature field summary from a completed thermal run. The 'thermal' qualifier separates it from modal/buckling/results siblings, though it never names fem_results, fem_result_probe, or render_fem_results as the alternatives an agent might confuse it with.

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?

"from a completed thermal run" and "Pass `analysis`, or the `job_id` of a finished fem_run_submit solve" give the precondition and input routing, which implies when to use it. There is no explicit when-not, and no sibling is named as an alternative path for non-thermal or in-progress runs, so guidance stops short of routing.

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