Skip to main content
Glama
Sign In
mcp-openems

mcp-openems

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

openems_create_helix

Create an axial-mode helical antenna design for circular polarization by specifying center frequency, turns, and optional name. Generates dimensions and simulation-ready script for openEMS.

Instructions

Design an axial-mode helical antenna for circular polarization.

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

Input Schema

NameRequiredDescriptionDefault
nameNoDesign name
turnsNoNumber of turns (more turns = higher gain)
frequency_ghzYesCenter frequency in GHz

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the purpose and does not mention what the tool returns, whether it modifies a design library, or any side effects.

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 a single sentence, front-loaded with the main purpose, and contains no unnecessary words.

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?

The tool has no output schema and no annotations, so the description should convey what happens when invoked. It lacks information about return values, side effects, or prerequisites, making it incomplete for a create operation.

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 already provides 100% coverage of parameter descriptions, so the description adds no extra parameter semantics. The mention of circular polarization is a design characteristic, not a parameter clarification.

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 designs an axial-mode helical antenna for circular polarization, using a specific verb and resource. It differentiates from sibling create tools by specifying the antenna type and mode.

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 provides no explicit guidance on when to use this over alternatives. It implies the tool is for helical antenna design but does not mention contrasting with other antenna types or any prerequisites.

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