AgentFEM
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTFEM_COMMAND | No | Absolute path to a specific agentfem executable. Use if a desktop app cannot see the activated conda environment. | |
| AGENTFEM_MCP_ROOTS | No | Approved project roots separated by the platform path separator. If not set, the server restricts access to its working directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| describe_systemA | Inspect the installed AgentFEM runtime and approved roots. Use summary first; request full only when selecting an advanced capability. |
| create_projectB | Create a new project from one version-matched official AgentFEM template inside an approved root. |
| validate_projectA | Run fail-closed structural and compatibility checks without solving the project. |
| inspect_projectA | Read project validation and recent immutable run identities without modifying the project. |
| submit_runB | After preflight, start a finite-element run in a separate process and return a durable job identity immediately. |
| get_run_statusB | Read one submitted run's status and any AgentFEM execution evidence currently available. |
| get_result_summaryA | Read the structured scientific result for a completed job or the project's latest run, including its trust state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool addresses a distinct phase: system description, project creation, validation, inspection, run submission, status retrieval, and result summary. No overlap in purposes, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., describe_system, create_project, submit_run). The naming convention is uniform and predictable.
Seven tools is well-scoped for a finite-element analysis server, covering the essential lifecycle without redundancy or bloat. Each tool earns its place.
The core workflow is covered: system inspection, project creation, validation, run submission, status checking, and result retrieval. Minor gaps like project updates or deletion exist but are not critical to the main simulation flow.