Skip to main content
Glama
TocharianOU

Kibana MCP Server

by TocharianOU

get_status

Retrieve the status of the Kibana server, including multi-space support, by specifying the target space or using the default configuration.

Instructions

Get Kibana server status with multi-space support

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNoTarget Kibana space (optional, defaults to configured space)

Implementation Reference

  • The asynchronous handler function that executes the tool logic: fetches Kibana server status via kibanaClient.get('/api/status'), formats the response with space context, handles errors gracefully.
    async ({ space }): Promise<ToolResponse> => {
      try {
        const targetSpace = space || defaultSpace;
        const response = await kibanaClient.get('/api/status', { space });
        return {
          content: [
            {
              type: "text",
              text: `[Space: ${targetSpace}] Kibana server status: ${JSON.stringify(response, null, 2)}`
            }
          ]
        };
      } catch (error) {
        console.error(`Failed to get server status: ${error}`);
        return {
          content: [
            {
              type: "text",
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }
          ],
          isError: true
        };
      }
    }
  • Zod input schema defining an optional 'space' parameter for targeting specific Kibana spaces.
    z.object({
      space: z.string().optional().describe("Target Kibana space (optional, defaults to configured space)")
    }),
  • Tool registration using server.tool(), including name, description, schema, and handler function.
      "get_status",
      `Get Kibana server status with multi-space support`,
      z.object({
        space: z.string().optional().describe("Target Kibana space (optional, defaults to configured space)")
      }),
      async ({ space }): Promise<ToolResponse> => {
        try {
          const targetSpace = space || defaultSpace;
          const response = await kibanaClient.get('/api/status', { space });
          return {
            content: [
              {
                type: "text",
                text: `[Space: ${targetSpace}] Kibana server status: ${JSON.stringify(response, null, 2)}`
              }
            ]
          };
        } catch (error) {
          console.error(`Failed to get server status: ${error}`);
          return {
            content: [
              {
                type: "text",
                text: `Error: ${error instanceof Error ? error.message : String(error)}`
              }
            ],
            isError: true
          };
        }
      }
    );
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 what the tool does but lacks behavioral details: it doesn't specify if this is a read-only operation, what permissions are required, whether it affects system state, rate limits, or what the output format looks like (e.g., JSON structure, error handling). For a tool with no annotation coverage, this is a significant gap in transparency.

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 that front-loads the core purpose ('Get Kibana server status') and adds a key feature ('with multi-space support'). There is no wasted verbiage, and it's appropriately sized for a simple tool with one optional parameter.

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 low complexity (1 optional parameter, no output schema, no annotations), the description is minimally complete. It covers the basic purpose but lacks context on usage guidelines, behavioral traits, or output details. For a status-checking tool, it should ideally mention what 'status' entails (e.g., health metrics, version info) or how it differs from siblings, but it's adequate as a starting point.

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%, with the single parameter 'space' documented in the schema as optional and defaulting to configured space. The description adds minimal value beyond this by mentioning 'multi-space support', which implies the parameter's purpose but doesn't provide additional syntax or format details. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 ('Get') and resource ('Kibana server status'), making the purpose evident. It adds specificity with 'multi-space support' which distinguishes it from generic status tools. However, it doesn't explicitly differentiate from sibling tools like 'get_kibana_api_detail' or 'execute_kb_api', which might also retrieve status-related information.

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 mentions 'multi-space support' but doesn't explain if this is for checking overall server health, space-specific status, or when to prefer it over siblings like 'get_available_spaces' or 'execute_kb_api'. No explicit when/when-not instructions or prerequisites are included.

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

Related 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/TocharianOU/mcp-server-kibana'

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