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

mcp-nec2-antenna

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nec2_get_nec_cards

Retrieve the raw NEC2 card deck for a given antenna design to edit manually or use with external tools.

Instructions

Get the raw NEC2 card deck for an antenna design (for manual editing or external tools).

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": {
      "antenna_id": "<antenna_id>"
    },
    "name": "nec2_get_nec_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
antenna_idYesAntenna ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It describes a read operation but does not disclose potential permissions or side effects. Given the tool's simplicity, the description is adequate but not rich.

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?

A single, well-structured sentence that conveys the tool's purpose and use cases without any extraneous information. Every word earns its place.

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?

For a simple tool with one parameter, no output schema, and no nested objects, the description is complete. It explains what the tool does and why it would be used, fulfilling all necessary context.

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?

Only one parameter (antenna_id) with 100% schema description coverage. The description adds no additional meaning beyond the schema, so baseline score of 3 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?

The description clearly states it retrieves the raw NEC2 card deck for an antenna design, with specific use cases (manual editing or external tools). It distinguishes itself from siblings like nec2_simulate and nec2_list_antennas.

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?

Explicitly mentions when to use: for manual editing or external tools. While it doesn't state when not to use, the context is sufficiently clear for an agent to choose appropriately among sibling tools.

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