netlogger-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETLOGGER_MCP_MOCK | No | Set to 1 to answer from bundled synthetic samples for testing without the network. | |
| NETLOGGER_MCP_CALLSIGN | No | Your callsign. Set to override the saved callsign. The server can also ask for it on first use and save it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get netlogger-mcp's version, the NetLogger API version it is built for, and the version of the records it returns. Returns: service_name, service_version (PyPI), spec_version (NetLogger API), contract_version. |
| netlogger_set_callsignA | Save the user's amateur radio callsign. Needed once, before the first lookup. NetLogger is told which station is asking, in every request, so it can tell one user from another. Ask the user for their own callsign; don't guess it. |
| netlogger_active_netsC | List nets on the air now. |
| netlogger_checkinsA | Get a live net's check-in list, and the pointer: the serial number of the station net control is working now. |
| netlogger_past_netsA | List closed nets over the last few days, with the net IDs netlogger_past_checkins needs. |
| netlogger_past_checkinsB | Get a closed net's check-in list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: version info, user setup, active nets, live check-ins, past nets, and past check-ins. No two tools overlap in function, and descriptions make the active/live vs past/closed distinction explicit.
All tool names use snake_case, and five of six follow a netlogger_verb_noun pattern. The lone get_version_info breaks the prefix convention, but the deviation is minor and doesn't hinder readability.
Six tools is a well-scoped set for a read-only NetLogger client, covering setup, discovery, and retrieval for both active and past nets. Each tool earns its place without redundancy.
The surface covers version info, user identification, active/past net listing, and check-in retrieval, which is a complete read lifecycle. However, there is no tool to submit a check-in or retrieve detailed net metadata, which may be a gap depending on intended use.