Skip to main content
Glama
sbrunner-atx

contest-mcp

by sbrunner-atx

log

Set call and exchange fields, run dupe checks, and log amateur-radio QSOs into N3FJP contest logging software.

Instructions

Logbook entry: set fields, run Call-tab, and ENTER a QSO. The headline tool.

operations:

  • log_qso: the automatic-logging flow. Provide call (and usually exchange, a dict of friendly field names → values, e.g. {"class": "2A", "section": "CT"}). Sets the call, runs CALLTAB (dupe check + lookups) unless calltab=false, sets the exchange, then ENTER. Returns the number of records added and any dupe response.

  • set (field, value): write one entry box.

  • set_many (fields={...}): write several entry boxes.

  • calltab: run CALLTAB (after setting the call).

  • enter: log the current form. Returns records_added plus a logged boolean derived from the QSO-count delta / ENTEREVENT — trust logged, not records_added, which can report 0 on success in networked mode. Do not retry when logged=true (creates duplicates).

  • clear: clear the entry form.

  • focus (field): move focus to a box (e.g. to auto-fill default RST).

Tip: contest (e.g. "field_day", "cq_wpx") lets the tool warn if the exchange is missing a field that contest needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callNo
fieldNo
valueNo
fieldsNo
calltabNo
contestNo
exchangeNo
operationYes
Behavior5/5

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

With no annotations, the description fully discloses behaviors: return values (records_added, logged boolean), side effects (dupe creation on retry), conditional execution (calltab=false skips lookups), and reliability notes (trust logged over records_added).

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 well-organized with bullet points for each operation and front-loaded purpose. It is slightly lengthy but every sentence adds value; minor redundancy could be trimmed.

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

Completeness4/5

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

Given the tool's complexity (8 parameters, 6 operations, no output schema), the description covers behavior, return values, reliability tips, and contest validation. It lacks explicit error scenarios or full return format details for each operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no descriptions (coverage 0%), but the description adds significant meaning for parameters like call, exchange (dict), calltab (default true), and contest. It could still be more systematic in documenting all parameter constraints.

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 is the headline tool for logging QSOs, enumerates distinct operations (log_qso, set, calltab, etc.), and distinguishes itself from siblings like status and query as the primary logging tool.

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?

The description explains when to use each operation and includes warnings (e.g., do not retry when logged=true). However, it does not explicitly advise against using this tool for non-logging tasks or when alternatives like search would be better.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sbrunner-atx/n3fjp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server