Skip to main content
Glama
Sign In
COMSOL MCP Server

COMSOL MCP Server

by Zhangyoupeng1996
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

troubleshoot

Get troubleshooting suggestions for common COMSOL errors including geometry build failures, mesh issues, solver non-convergence, memory errors, and license problems.

Instructions

Get troubleshooting suggestions for common issues.

Common error types:

  • "geometry_build_failed": Geometry sequence failed to build

  • "mesh_failed": Mesh generation failed

  • "solver_no_convergence": Solver did not converge

  • "memory_error": Out of memory

  • "license_error": COMSOL license issues

Args: error_type: Type of error encountered context: Additional context about the error

Returns: Troubleshooting suggestions

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": {
      "error_type": "<error_type>"
    },
    "name": "troubleshoot"
  }
}

Input Schema

NameRequiredDescriptionDefault
error_typeYes
contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. The description lacks details about side effects, prerequisites, or limitations. It only mentions returning suggestions, but no behavioral context beyond that.

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?

The description is well-structured with a list of error types and Args/Returns sections. The first sentence conveys the core purpose. Slightly redundant with schema but overall efficient.

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

Completeness2/5

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

No output schema exists, yet the description only says 'Returns: Troubleshooting suggestions' without specifying format, examples, or how suggestions are provided. Incomplete for a diagnostic tool.

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?

The schema has 0% description coverage, but the description lists common values for error_type, adding some meaning. However, context remains vague ('Additional context') and no format constraints are given.

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?

The description clearly states the tool provides troubleshooting suggestions for common issues, with a list of error types. It is unique among sibling tools, which focus on other COMSOL operations.

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?

No explicit guidance on when to use this tool over alternatives, or when not to use it. Usage is implied only when encountering errors.

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