Skip to main content
Glama
Sign In
COMSOL MCP Server

COMSOL MCP Server

by Zhangyoupeng1996
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

param_description

Retrieve or update the description text of a parameter in a COMSOL model. Provide a new text to update, or leave blank to read the current description.

Instructions

Get or set the description of a parameter.

Args: name: Parameter name text: New description text (if None, returns current description) model_name: Model name (default: current model)

Returns: Parameter description, or confirmation of update

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

Input Schema

NameRequiredDescriptionDefault
nameYes
textNo
model_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool can get or set based on the 'text' parameter and returns either description or confirmation, but lacks detail on side effects (e.g., overwriting) or confirmation format.

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 concise with a clear top-level statement, structured Args, and Returns. Every sentence adds value, and there is no unnecessary text.

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 simple get/set tool, the description covers the main purpose and parameters. The return value is stated ('Parameter description, or confirmation of update'), though more specific format details could improve completeness. Given no output schema, this is adequate.

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 0%, but the description clearly explains each parameter: 'name' (parameter name), 'text' (new description, returns current if None), and 'model_name' (model name, default current). This adds meaning beyond the schema.

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 'Get or set the description of a parameter,' specifying the action (get/set) and the resource (parameter description). It distinguishes from sibling tools like param_get and param_set, which deal with parameter values.

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

Usage Guidelines3/5

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

The description implies usage for getting or setting parameter descriptions but lacks explicit guidance on when to use this tool versus alternatives like param_get or param_set. No exclusions or alternative references are provided.

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