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

mcp-nec2-antenna

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nec2_create_loop

Create a full-wave loop antenna (quad configuration) for a given frequency and height above ground. Generates a NEC2 model for simulation.

Instructions

Create a full-wave loop antenna (quad configuration).

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_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAntenna name
frequency_mhzYesDesign frequency in MHz
height_mNoHeight above ground in meters (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations available; description lacks details on side effects, permissions, or what the antenna creation entails beyond the action itself.

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?

Single sentence with zero wasted words, clearly stating verb and resource.

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?

Lacks critical context: no output schema, no explanation of 'quad configuration', no prerequisites or constraints beyond parameters.

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 covers all parameters with descriptions; description adds no extra meaning beyond the schema, so baseline score applies.

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?

Description clearly states the tool creates a full-wave loop antenna (quad configuration), distinguishing it from siblings like dipoles or verticals.

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 guidance on when to use this tool versus alternatives (e.g., when a loop is preferred over a dipole). No exclusions or context 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