Skip to main content
Glama
dhhuston

APRS.fi MCP Server

by dhhuston

track_multiple_callsigns

Monitor multiple ham radio callsigns simultaneously to track positions and support balloon chase operations using APRS.fi data.

Instructions

Track multiple callsigns at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callsignsYesArray of callsigns to track
apiKeyNoAPRS.fi API key (optional if set via /set-api-key)

Implementation Reference

  • MCP tool handler in the CallToolRequestSchema switch statement that invokes the getMultiplePositions service method and formats the response as JSON text content.
    case 'track_multiple_callsigns':
      const multiplePositions = await this.aprsService.getMultiplePositions(
        args.callsigns as string[],
        args.apiKey as string
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(multiplePositions, null, 2),
          },
        ],
      };
  • Core implementation of tracking multiple callsigns: validates input, constructs API request to APRS.fi with comma-separated callsigns, fetches and parses position data, handles errors.
    async getMultiplePositions(callsigns: string[], apiKey?: string): Promise<APRSPosition[]> {
      const keyToUse = apiKey || this.apiKey;
      if (!keyToUse) {
        throw new APRSError('APRS API key not provided. Use /set-api-key command or provide apiKey parameter.');
      }
    
      if (!callsigns?.length) {
        return [];
      }
    
      const cleanCallsigns = callsigns
        .map(c => c.trim().toUpperCase())
        .filter(c => c.length > 0);
    
      if (cleanCallsigns.length === 0) {
        return [];
      }
    
      const params = new URLSearchParams({
        name: cleanCallsigns.join(','),
        what: 'loc',
        apikey: keyToUse,
        format: 'json'
      });
    
      try {
        const response = await fetch(`${this.baseUrl}?${params}`);
        
        if (!response.ok) {
          throw new APRSError(
            `APRS API request failed: ${response.status} ${response.statusText}`,
            response.status
          );
        }
    
        const data: APRSResponse = await response.json();
    
        if (data.result !== 'ok') {
          throw new APRSError(`APRS API error: ${data.result}`);
        }
    
        return data.entries.map(entry => ({
          ...entry,
          timestamp: entry.timestamp * 1000,
        }));
    
      } catch (error) {
        if (error instanceof APRSError) {
          throw error;
        }
        
        if (error instanceof TypeError && error.message.includes('fetch')) {
          throw new APRSError('Network error: Unable to connect to APRS.fi API. Check your internet connection.');
        }
        
        throw new APRSError(`Unexpected error: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • index.ts:330-349 (registration)
    Tool registration in ListToolsRequestSchema handler, defining name, description, and input schema.
      name: 'track_multiple_callsigns',
      description: 'Track multiple callsigns at once',
      inputSchema: {
        type: 'object',
        properties: {
          callsigns: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'Array of callsigns to track',
          },
          apiKey: {
            type: 'string',
            description: 'APRS.fi API key (optional if set via /set-api-key)',
          },
        },
        required: ['callsigns'],
      },
    },
  • Input schema defining required 'callsigns' array and optional 'apiKey' string.
    inputSchema: {
      type: 'object',
      properties: {
        callsigns: {
          type: 'array',
          items: {
            type: 'string',
          },
          description: 'Array of callsigns to track',
        },
        apiKey: {
          type: 'string',
          description: 'APRS.fi API key (optional if set via /set-api-key)',
        },
      },
      required: ['callsigns'],
    },
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 states the tool tracks callsigns but doesn't disclose behavioral traits such as what 'track' entails (e.g., real-time monitoring, batch processing), rate limits, authentication needs (beyond the optional apiKey in schema), or output format. This leaves significant gaps for a tool with potential real-time or API interactions.

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 single, efficient sentence with zero waste. It's appropriately sized and front-loaded, clearly stating the core functionality without unnecessary elaboration.

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?

Given the complexity of tracking multiple callsigns (likely involving API calls and real-time data), no annotations, and no output schema, the description is incomplete. It doesn't explain what 'track' means operationally, what the tool returns, or any constraints, making it inadequate for informed use by an AI agent.

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%, so the schema already documents both parameters (callsigns as an array of strings, apiKey as optional). The description adds no additional meaning beyond what's in the schema, such as format details or usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('track') and resource ('multiple callsigns'), specifying it handles multiple items at once. However, it doesn't distinguish this tool from its siblings (get_aprs_history, get_aprs_position, validate_aprs_key), which appear to be related APRS operations but have different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing an API key, nor does it explain how this differs from sibling tools (e.g., tracking vs. getting history or position). Usage context is implied but not explicit.

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/dhhuston/APRSFI-MCP-SERVER'

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