Skip to main content
Glama

get_system_status

Retrieve current system status and available capabilities for aviation operations, including airport data and aircraft performance tools.

Instructions

Get system status and capabilities.

Returns: JSON string with system status information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the get_system_status tool. It constructs and returns a JSON string detailing the Aerospace MCP Server's status, version, capabilities including airport search, flight planning, distance calculation, and OpenAP performance availability.
    def get_system_status() -> str:
        """Get system status and capabilities.
    
        Returns:
            JSON string with system status information
        """
        status = {
            "system": "Aerospace MCP Server",
            "version": "0.1.0",
            "status": "operational",
            "capabilities": {
                "airport_search": True,
                "flight_planning": True,
                "great_circle_distance": True,
                "openap_performance": OPENAP_AVAILABLE,
            },
            "optional_features": {
                "openap_available": OPENAP_AVAILABLE,
            },
        }
    
        if OPENAP_AVAILABLE:
            status["openap_info"] = {
                "description": "OpenAP aircraft performance modeling available",
                "supported_aircraft": "A319, A320, A321, A332, A333, A343, A346, A359, A388, B737, B738, B739, B744, B747, B752, B753, B762, B763, B772, B773, B777, B787, and more",
            }
        else:
            status["openap_info"] = {
                "description": "OpenAP not available - install with: pip install openap",
                "note": "Flight planning will work without performance estimates",
            }
    
        return json.dumps(status, indent=2)
  • Registration of the get_system_status tool handler in the FastMCP server using the mcp.tool decorator/method.
    mcp.tool(get_system_status)
  • Import of the get_system_status function from tools.core module in the FastMCP server, necessary for registration.
    from .tools.core import (
        calculate_distance,
        get_aircraft_performance,
        get_system_status,
        plan_flight,
        search_airports,
    )
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool returns (JSON string with system status information) but doesn't describe what 'system status' includes, whether it's real-time or cached data, authentication requirements, rate limits, or potential side effects.

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?

The description is appropriately brief with two sentences that directly address purpose and return format. It's front-loaded with the core functionality and avoids unnecessary elaboration, though the second sentence could be integrated more smoothly.

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?

Given the tool has no parameters, an output schema exists, and no annotations, the description provides basic but incomplete context. It states what the tool does and the return format, but doesn't explain what 'system status' means in this aerospace/engineering context or what specific capabilities are reported.

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 0 parameters with 100% schema description coverage, so the schema already fully documents the input requirements. The description appropriately doesn't add parameter information beyond what's already covered by the empty schema, earning a baseline score of 4 for zero-parameter tools.

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's purpose with a specific verb ('Get') and resource ('system status and capabilities'), making it immediately understandable. However, it doesn't differentiate from sibling tools, which are all aerospace/engineering focused but none appear to directly overlap with system status retrieval.

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, appropriate contexts, or exclusions, leaving the agent to infer usage from the tool name alone.

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/cheesejaguar/aerospace-mcp'

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