Skip to main content
Glama
Sign In
COMSOL MCP Server

COMSOL MCP Server

by Zhangyoupeng1996
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

geometry_get_boundaries

Retrieve all boundaries from a COMSOL geometry with their numbers and areas to identify faces before applying boundary conditions.

Instructions

Get all boundaries from a geometry with their properties.

Use this to identify which boundary numbers correspond to which faces before setting boundary conditions.

Args: geometry_name: Geometry sequence name (default: first geometry) model_name: Model name (default: current model)

Returns: List of boundaries with their numbers and areas

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": "geometry_get_boundaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
geometry_nameNo
model_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It states the return value ('List of boundaries with their numbers and areas') and implies a read-only operation with no side effects, which is transparent.

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 (5 lines) and front-loaded with purpose, then usage guidance, then parameters. Every sentence adds value.

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

Completeness5/5

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

Despite no output schema, the description includes return value details. It covers purpose, when to use, and parameter meanings, making it complete for a simple retrieval tool.

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?

The input schema has 0% description coverage (only titles). The description adds meaning by listing both parameters with their defaults ('geometry_name: Geometry sequence name (default: first geometry)'), significantly augmenting 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 all boundaries from a geometry with their properties,' specifying the verb and resource. It differentiates from sibling geometry tools like 'geometry_list' or 'geometry_list_features' by focusing on boundaries.

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 explicitly advises using this tool 'to identify which boundary numbers correspond to which faces before setting boundary conditions,' providing clear context. While it doesn't list when not to use it or alternatives, the guidance is strong.

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