Skip to main content
Glama

get status

Check the operational status of the TabNews API to verify service availability and connectivity.

Instructions

get status from tabnews api

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get status' tool. It fetches the API status using getApiStatus(), formats it as JSON text, and returns it wrapped in an McpResponse.
    handler: async (): Promise<McpResponse> => {
      try {
        const result = await getApiStatus();
    
        const content: McpTextContent = {
          type: "text",
          text: `API Status:\n\n${JSON.stringify(result, null, 2)}`,
        };
    
        return {
          content: [content],
        };
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(`Failed to check API status: ${error.message}`);
        } else {
          throw new Error("Failed to check API status");
        }
      }
    },
  • src/index.ts:24-29 (registration)
    Registration of the 'get status' tool (checkStatusTool) with the MCP server using server.tool().
    server.tool(
      checkStatusTool.name,
      checkStatusTool.description,
      checkStatusTool.parameters,
      checkStatusTool.handler
    );
  • Helper function getApiStatus() that fetches the status from the TabNews API endpoint /status.
    export async function getApiStatus(): Promise<GetStatusResponse> {
      const response = await fetch(`${TABNEWS_API_URL}/status`);
      const data = await response.json();
    
      return data as GetStatusResponse;
    }
  • Type definition for the GetStatusResponse returned by the API status endpoint, used in the tool handler.
    export interface GetStatusResponse {
      updated_at: string;
      dependencies: Dependencies;
    }
  • MCP response type used by the tool handler to structure the output.
    export interface McpResponse {
      content: McpContent[];
      _meta?: Record<string, unknown>;
      isError?: boolean;
      [key: string]: unknown;
    }
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 only states the basic action without disclosing behavioral traits such as rate limits, authentication needs, response format, or error handling. This is inadequate for a tool with zero annotation coverage.

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 ('get status from tabnews api') with no wasted words, front-loading the core purpose. It is appropriately sized for a simple, parameterless tool.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'status' entails, the return values, or any behavioral context, leaving significant gaps for an AI agent to understand and use the tool effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate, earning a baseline score of 4 for tools with no parameters.

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

Purpose3/5

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

The description 'get status from tabnews api' states the action ('get') and resource ('status from tabnews api'), but is vague about what 'status' specifically refers to (e.g., API health, system status, user status). It does not differentiate from sibling tools like 'get content' or 'get comments', which also retrieve data from the same API.

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. The description does not mention context, prerequisites, or exclusions, and with sibling tools like 'get content' or 'get comments' available, there is no indication of when 'get status' is appropriate.

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/renant/mcp-tabnews'

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