Skip to main content
Glama

FEM New Analysis

fem_new_analysis

Creates a Fem::FemAnalysis container for setting up FEM simulations and returns its handle and name.

Instructions

Create a Fem::FemAnalysis container. Returns {handle, name}.

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

Input Schema

NameRequiredDescriptionDefault
nameNoAnalysis
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. First observed

TDQS

B3.3/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 the safety profile is covered. The description adds the return shape {handle, name}, which is genuinely useful since there is no output schema, but it omits whether the container is attached to the active document, whether repeated calls create duplicates, and whether the handle is required by downstream fem_* calls.

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?

Two short sentences with the action and return contract front-loaded; nothing is wasted or buried.

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?

For a zero-required-parameter creation tool with no output schema, disclosing the {handle, name} return is a meaningful addition. However, in a suite with dozens of fem_* siblings, the description leaves the agent without the prerequisite/workflow context needed to place this call correctly in a FEM setup sequence.

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 50%: the workspace parameter is documented in the schema, but the name parameter (default "Analysis") has no description. The description's mention of name only appears in the return tuple, so it hints that the argument labels the analysis but never confirms it; baseline 3 fits given partial schema coverage.

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 ("Create") and a specific resource ("Fem::FemAnalysis container"), which is unambiguous about what the call produces. It does not differentiate from the many sibling fem_* tools (fem_set_solver, fem_mesh, fem_run), so an agent cannot tell from the text that this is the container-creation step that precedes them.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus other FEM siblings, no ordering information (e.g., that solver/material/mesh calls need an existing analysis), and no prerequisites such as requiring an open document. The agent must infer the workflow entirely from the tool name.

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