list_all_bands
Listet alle verfügbaren Amateurfunkbänder mit Grundinformationen auf
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
oeradio-mcp
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read-only list operation but does not clarify what 'basic information' includes, return format, or potential limitations. The behavior is mostly implicit.
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?
The description is a concise single sentence in German with no redundant words. It is front-loaded with the main action and efficient.
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?
For a simple zero-parameter list tool, the description provides a basic idea but leaves ambiguity about what 'basic information' entails and what the return structure looks like. Without an output schema, this vagueness makes the description only minimally complete.
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 tool has zero parameters, and the schema trivially covers this. No parameter details are needed, and the description adds none, but the baseline for a no-parameter tool is 4.
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?
The description clearly states the tool lists all available amateur radio bands with basic information, using a specific verb ('listet') and resource ('Amateurfunkbänder'). It does not explicitly distinguish from sibling tools like get_band_plan, but the purpose is unambiguous.
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?
No guidance is provided on when to use this tool versus alternatives such as get_band_plan or check_frequency. The description only states what the tool does, without specifying use cases, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation5/5
Each tool targets a distinct operation: calculations for different physical quantities, separate callsign functions for lookup, validation, suggestion, and availability, and band plan queries. No two tools appear to perform the same action, making selection unambiguous.
Naming Consistency3/5
Most tools follow a verb_noun convention (calculate_, check_, list_), but the callsign_* group consistently places the noun first (callsign_lookup, callsign_validate). This split is readable but represents a mixed convention that slightly reduces predictability.
Tool Count3/5
With 17 tools, the server is above the ideal 3-15 range and falls into the borderline 'feels heavy' category. While every tool has a distinct purpose, the number may be slightly unwieldy for quick selection.
Completeness4/5
The toolkit covers a broad range of amateur radio calculations (battery, cable, EIRP, wavelength, SWR, power) and callsign operations (lookup, validate, suggest, availability, database info). Some advanced features like propagation prediction are absent, but the core domain is well covered without critical gaps.