Skip to main content
Glama

get_infrastructure_status

Check infrastructure health and status for MCP servers on Fly.io and Cloudflare Workers. View current state, active locks, and operation history to monitor deployments and track changes.

Instructions

Get comprehensive overview of entire infrastructure. Safe read-only operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_historyNoInclude recent operation history (default: true)
include_locksNoInclude active locks (default: true)

Implementation Reference

  • Handler implementation for the get_infrastructure_status tool. Parses input arguments and invokes the orchestrator script with the 'status/infrastructure' operation.
    case "get_infrastructure_status": {
      const { include_history, include_locks } = args as {
        include_history?: boolean;
        include_locks?: boolean;
      };
      
      const params: Record<string, string> = {
        include_history: String(include_history !== false),
        include_locks: String(include_locks !== false)
      };
      
      result = executeOrchestrator("status/infrastructure", params);
      break;
    }
  • Tool definition including name, description, and input schema for get_infrastructure_status. Used for tool listing and validation.
    {
      name: "get_infrastructure_status",
      description: "Get comprehensive overview of entire infrastructure. Safe read-only operation.",
      inputSchema: {
        type: "object",
        properties: {
          include_history: {
            type: "boolean",
            description: "Include recent operation history (default: true)"
          },
          include_locks: {
            type: "boolean",
            description: "Include active locks (default: true)"
          }
        }
      }
    }
  • Shared utility function executeOrchestrator that runs python orchestrator.py for infrastructure operations, used by get_infrastructure_status handler.
    function executeOrchestrator(operation: string, params: Record<string, string> = {}): any {
      const paramStr = Object.entries(params)
        .map(([key, value]) => `${key}="${value}"`)
        .join(" ");
      
      const cmd = `cd ${ORCHESTRATOR_PATH} && python orchestrator.py ${operation} ${paramStr}`;
      
      try {
        const output = execSync(cmd, {
          encoding: "utf-8",
          maxBuffer: 10 * 1024 * 1024
        });
        
        // Try to parse as JSON, fallback to plain text
        try {
          return JSON.parse(output);
        } catch {
          return { output: output.trim() };
        }
      } catch (error: any) {
        return {
          success: false,
          error: error.message,
          stderr: error.stderr?.toString() || "",
          stdout: error.stdout?.toString() || ""
        };
      }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Safe read-only operation', which clarifies that it's non-destructive and safe to use. However, it doesn't mention other behavioral aspects like performance implications, rate limits, or authentication needs, which would be helpful for a comprehensive infrastructure tool.

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 extremely concise with just two sentences that are front-loaded and waste no words. The first sentence states the purpose, and the second adds critical behavioral context, making it efficient and easy to parse.

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's complexity (infrastructure overview) and lack of annotations or output schema, the description is minimally adequate. It covers safety and purpose but doesn't explain what 'comprehensive overview' entails in terms of return values or structure, leaving gaps that the agent must 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?

The input schema has 100% description coverage, so the schema already fully documents the two parameters (include_history and include_locks). The description adds no additional parameter semantics beyond what the schema provides, making the baseline score of 3 appropriate as 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 tool's purpose with a specific verb ('Get') and resource ('comprehensive overview of entire infrastructure'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'check_services_health', which might overlap in functionality.

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 like 'check_services_health' or 'trigger_auto_recovery'. It lacks context about specific scenarios, prerequisites, or exclusions, leaving the agent to infer usage based on tool names 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/itsablabla/lastrock-mcp'

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