Skip to main content
Glama
Sign In
mcp-nec2-antenna

mcp-nec2-antenna

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nec2_create_dipole

Generate a half-wave dipole antenna design for simulation by specifying frequency, height, and wire radius. Returns an antenna ID for use with NEC2 analysis.

Instructions

Create a half-wave dipole antenna. Returns antenna ID for simulation.

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>",
      "frequency_mhz": "<frequency_mhz>"
    },
    "name": "nec2_create_dipole"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAntenna name
frequency_mhzYesDesign frequency in MHz (e.g., 146 for 2m band)
height_mNoHeight above ground in meters (default: 10)
wire_radius_mmNoWire radius in mm (default: 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description carries full burden. It mentions returning an antenna ID but omits side effects (e.g., saving, mutating state), required permissions, or any destructive potential. For a creation tool, more behavioral context is needed.

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 two concise sentences, front-loaded with the main action and result. No unnecessary words.

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

Completeness3/5

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

With 4 parameters, no output schema, and no annotations, the description is adequate but minimal. It does not explain return format, error cases, or constraints (e.g., frequency range). For a simple creation tool, it covers essentials but leaves gaps.

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?

Schema coverage is 100%, so parameters are documented. The description adds 'half-wave dipole' context implying frequency determines length, but does not elaborate on how parameters like height or wire radius affect the antenna. Baseline 3 is appropriate.

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 specifies the action ('create'), the resource ('half-wave dipole antenna'), and the return value ('antenna ID for simulation'). It distinguishes from sibling tools by naming the specific antenna type (dipole vs inverted_v, loop, vertical, yagi).

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?

The description provides no guidance on when to use this tool versus alternatives, such as recommending a dipole for simple omni-directional coverage or pointing to nec2_create_yagi for gain. No when-not-to-use or alternative suggestions.

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