Skip to main content
Glama

FEM Result Probe

fem_result_probe
Read-only

Query FEM stress, displacement, or temperature at a specific point or CAD face instead of only global maxima, enabling localized design iteration.

Instructions

Probe FEM results at a specific location, instead of only the global max + top-N that fem_results returns. Answers "what is the stress at this point / on this face?" — the agent-friendly form for design iteration.

Pick exactly one mode:

  • POINT: point=[x, y, z] (mm, model coordinates). Interpolates the field barycentrically inside the tet containing the point (method='interpolated'); if the point is outside the mesh it falls back to the nearest node and reports distance_mm (method='nearest_node').

  • FACE: handle= + face=<'f_*' tag or 'FaceN'>. Aggregates the field over the mesh nodes on that CAD face, returning {min, max, mean}.

field: 'auto' (default — every field present in the result) | 'vonmises' | 'displacement' | 'temperature'.

Pass analysis, or the job_id of a finished fem_run_submit solve.

Returns (point mode) {mode:'point', query_point, method, element_id?, node?, distance_mm, vonmises_mpa?, displacement_mm?, displacement_vector?, temperature_c?}; (face mode) {mode:'face', face, node_count, vonmises_mpa?:{min,max,mean}, displacement_mm?:{...}, temperature_c?:{...}}.

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_result_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
faceNo
fieldNoauto
pointNo
handleNo
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

A4.9/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: it discloses the interpolation method (barycentric within the containing tet), the out-of-mesh fallback to nearest node with a distance_mm report, and that FACE aggregates over mesh nodes on a CAD face as {min,max,mean}. These are behavioral details an agent cannot get from the annotations or schema.

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-loads the contrast with `fem_results`, then structures the two modes as bullets, so scanning is fast. It runs long and the 'agent-friendly form for design iteration' framing is decorative, but with no output schema the return-shape section earns its space.

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

Completeness5/5

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

All seven optional parameters are accounted for, the two mutually exclusive modes are fully specified, and because there is no output schema the description documents both return payloads (point and face) field by field. Nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema description coverage is only 14%, but the description compensates for nearly every parameter: point units/orientation (mm, model coordinates), face tag syntax ('f_*' or 'FaceN'), handle semantics, the full field enum ('auto' | 'vonmises' | 'displacement' | 'temperature'), and the analysis-vs-job_id choice. Only `workspace` is left to the schema, which already documents it.

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?

Names a specific verb+resource (probe FEM results at a specific location) and immediately contrasts it with the sibling `fem_results`, which only returns global max + top-N. The parenthetical question ('what is the stress at this point / on this face?') pins down the exact job an agent would route here.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Pick exactly one mode' and gives the required arguments for each: POINT needs point=[x,y,z], FACE needs handle + face. It also states the alternative (`fem_results`) and the condition that selects it, plus that a finished `fem_run_submit` job_id or an `analysis` can be supplied.

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