Skip to main content
Glama
Sign In
netlogger-mcp

netlogger-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Netlogger Past Checkins

netlogger_past_checkins
Read-onlyIdempotent

Retrieves the check-in list for a closed amateur-radio net using its server, name, and ID.

Instructions

Get a closed net's check-in list.

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": {
      "server_name": "<server_name>",
      "net_name": "<net_name>",
      "net_id": "<net_id>"
    },
    "name": "netlogger_past_checkins"
  }
}

Input Schema

NameRequiredDescriptionDefault
net_idYesThe net ID, from netlogger_past_nets.
net_nameYesThe net's name, from netlogger_past_nets.
server_nameYesThe net's server, from netlogger_past_nets.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, and the description adds no behavioral context beyond that — no note on result size, pagination, or what happens if the net is still active. The one extra implication ('closed') is worth little on its own.

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?

A single front-loaded sentence with no filler. It is efficient but sits close to under-specification, which is penalized elsewhere rather than here.

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

Completeness3/5

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

An output schema and full annotation coverage carry most of the load, and the schema documents where the three IDs come from. Still missing is the workflow context (you must first call netlogger_past_nets) and any distinction from netlogger_checkins, which the description alone leaves for the agent to infer.

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 description coverage is 100%, and each parameter already states it comes from netlogger_past_nets. The description adds nothing about the parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get a check-in list) and scopes it to a closed net, which distinguishes it from the sibling netlogger_checkins (active nets) in substance. It does not name the sibling it differs from, so the distinction must be inferred from the word 'closed'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage only through the word 'closed' — an agent must infer that this is for finished nets rather than live ones. It never states prerequisites (the net must already be ended) or points at alternatives like netlogger_checkins, though the schema descriptions do reference netlogger_past_nets for the IDs.

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