AetherLink SDR MCP

by N-Erickson

Overview Schema Source Related Servers Discussions Admin

Python

Local

pager_get_messages

Retrieve decoded pager messages, newest last, and filter by age or limit results to inspect recent radio transmissions.

Instructions

Get decoded pager messages (newest last)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pager_get_messages"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of messages to return
`max_age`	No	Only messages from the last N seconds; 0 for all

Output Schema

Name	Required	Description	Default
`active`	No
`messages`	No
`statistics`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does very little with it. It discloses only that messages are decoded and ordered newest-last; it says nothing about whether decoding must be running, whether results are buffered or consumed, or whether the call blocks or fails when no messages exist.

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, and the ordering note is a useful detail rather than padding. It is arguably too terse for a tool with no annotations, but nothing present is wasted.

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?

An output schema exists, so return values need not be described, and the parameters are fully covered by the schema. However, for a pipeline-dependent tool in a decoding workflow, the absence of any note about prerequisites or state makes the definition incomplete despite the low complexity.

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 both parameters (limit, max_age) are documented with defaults and units in the schema itself. The description adds no filtering or paging semantics beyond that, so the baseline of 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?

Names a specific verb and resource: 'Get decoded pager messages', which is clearly distinguishable from siblings like pager_start_decoding, pager_stop_decoding, and pager_find_frequencies. It also states the ordering convention 'newest last', though it does not explicitly contrast itself with any sibling.

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?

There is no when-to-use guidance. The description does not mention the prerequisite that pager decoding must be started via pager_start_decoding before messages exist, nor does it point to alternatives for other pager operations. Usage is only inferable from the 'Get' verb.

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