Skip to main content
Glama

get_status

Check the current national load shedding stage for Eskom and Cape Town to know the active stage right now.

Instructions

Get the current national load shedding stage for both Eskom and Cape Town. Use this to find out what stage we are on right now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
testNoUse test data instead of live data (does not count against your quota)

Implementation Reference

  • The actual implementation of getStatus — calls the EskomSePush API /status endpoint and returns the load shedding status (Eskom + Cape Town stages).
    async getStatus(test = false): Promise<LoadSheddingStatus> {
      const params = test ? { test: "current" } : {};
      const { data } = await this.http.get<LoadSheddingStatus>("/status", { params });
      return data;
    }
  • Type definition (LoadSheddingStatus) returned by getStatus, containing eskom and capetown status objects with name, stage, and stage_updated fields.
    export interface LoadSheddingStatus {
      status: {
        capetown: { name: string; stage: string; stage_updated: string };
        eskom: { name: string; stage: string; stage_updated: string };
      };
    }
  • src/index.ts:24-57 (registration)
    Tool registration via server.tool('get_status', ...) with Zod schema for optional 'test' parameter and handler that calls client.getStatus() and formats the result.
    server.tool(
      "get_status",
      "Get the current national load shedding stage for both Eskom and Cape Town. Use this to find out what stage we are on right now.",
      {
        test: z
          .boolean()
          .optional()
          .default(false)
          .describe("Use test data instead of live data (does not count against your quota)"),
      },
      async ({ test }) => {
        const data = await client.getStatus(test);
        const { eskom, capetown } = data.status;
    
        return {
          content: [
            {
              type: "text",
              text: [
                "## 🔌 Current Load Shedding Status",
                "",
                `**Eskom (National)**`,
                `  Stage: ${eskom.stage || "None (No load shedding)"}`,
                `  Last updated: ${eskom.stage_updated}`,
                "",
                `**City of Cape Town**`,
                `  Stage: ${capetown.stage || "None (No load shedding)"}`,
                `  Last updated: ${capetown.stage_updated}`,
              ].join("\n"),
            },
          ],
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states the tool fetches current status and mentions the test parameter (which is documented in the schema). It does not disclose update frequency, caching, or quota details beyond the test parameter's note.

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 two sentences, front-loaded with the purpose, and contains no unnecessary information. Every part is useful.

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?

The tool has an optional test parameter and no output schema. The description does not explain the return format (e.g., numeric stage, object with details), which is necessary for an agent to interpret the result correctly.

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 schema coverage is 100% for the single parameter (test), and its description is already in the schema. The tool description adds no additional meaning to the parameter, meeting the baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves the current national load shedding stage for both Eskom and Cape Town. It uses a specific verb 'get' and identifies the resource, which distinguishes it from sibling tools like get_area_schedule or get_areas_nearby.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for finding the current stage, but does not explicitly mention when not to use this tool or provide alternatives. The sibling tools exist for area-specific or schedule lookups, but no guidance is given.

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/zukhanyendiki9-code/eskomsepush-mcp'

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