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

mcp-nec2-antenna

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nec2_create_vertical

Design a quarter-wave vertical antenna with ground radials by specifying frequency and radial count.

Instructions

Create a quarter-wave vertical antenna with ground radials.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAntenna name
frequency_mhzYesDesign frequency in MHz
num_radialsNoNumber of ground radials (default: 4)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

The description lacks behavioral details beyond the act of creation. With no annotations, it does not disclose side effects, state changes, or what happens to existing data. It is too minimal for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is concise and to the point. It could be slightly more informative without losing conciseness, but it does not waste 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?

Given the absence of an output schema and the creation nature, the description fails to mention what the tool returns (e.g., antenna ID) or any prerequisites. It is incomplete for guiding an agent on full usage.

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?

All parameters (name, frequency_mhz, num_radials) are fully described in the input schema with 100% coverage. The description adds no extra meaning beyond the schema, so the baseline of 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 clearly states it creates a 'quarter-wave vertical antenna with ground radials,' specifying both the antenna type and configuration. This is a specific verb+resource that distinguishes it from sibling tools like dipoles and loops.

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 is provided on when to use this tool versus alternatives like nec2_create_dipole or nec2_create_yagi. The description implies usage for vertical antennas but does not explicitly state context or exclusions.

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