Skip to main content
Glama

FEM Mesh Refinement

fem_mesh_refinement

Adds a local refinement region to an existing FEM mesh, letting you specify faces or edges and a smaller characteristic length for targeted mesh density.

Instructions

Add a local mesh-refinement region to an existing FEM mesh.

mesh: handle of the FEM mesh. refs: list of {handle, face|edge|tag} dicts identifying the elements (faces/edges) to refine on. char_length: characteristic element length (mm) on those elements; should be smaller than the global mesh setting to actually refine.

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": {
      "mesh": "<mesh>",
      "refs": "<refs>",
      "char_length": "<char_length>"
    },
    "name": "fem_mesh_refinement"
  }
}

Input Schema

NameRequiredDescriptionDefault
meshYes
nameNoMeshRegion
refsYes
workspaceNoRun this call in this named workspace
char_lengthYes

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds the prerequisite of an existing mesh and the refinement condition for char_length, but it does not disclose whether the refinement is additive across repeated calls, whether it invalidates existing results, or how it interacts with the base mesh.

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?

The description is short and front-loaded: the first sentence states the core action, followed by concise parameter explanations. Every sentence adds useful information without repetition or 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 mutation tool with no output schema and five parameters, the description covers the essential required inputs and the key refinement condition. It is largely complete, though it could do more to explain the optional name parameter and the lifecycle impact of adding a refinement region.

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 description coverage is low (20%), so the description must compensate. It explains the mesh handle, the refs structure (list of dicts with handle and face/edge/tag), and char_length units and meaning, though it omits the optional name parameter and does not mention workspace beyond what the schema already says.

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 states a specific verb and resource: adding a local mesh-refinement region to an existing FEM mesh. It is clear what the tool does, but it does not explicitly name or differentiate itself from sibling tools such as fem_mesh, which likely performs global meshing.

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 provides clear usage context: it must be applied to an existing FEM mesh, and char_length should be smaller than the global mesh setting to actually refine. It does not specify when to use this versus alternatives or any exclusions, but the operative context is clear.

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