Skip to main content
Glama

server_info

Check server status and configuration to monitor the MCP AI Bridge server's operational state and settings.

Instructions

Get server status and configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'server_info' tool that collects and formats server information including configuration, available models, rate limits, and security settings.
    handleServerInfo() {
      const info = {
        name: process.env.MCP_SERVER_NAME || 'AI Bridge',
        version: process.env.MCP_SERVER_VERSION || '1.0.0',
        openai: {
          configured: !!this.openai,
          models: this.openai ? MODELS.OPENAI : [],
        },
        gemini: {
          configured: !!this.gemini,
          models: this.gemini ? MODELS.GEMINI : [],
        },
        rateLimits: {
          maxRequests: DEFAULTS.RATE_LIMIT.MAX_REQUESTS,
          windowMs: DEFAULTS.RATE_LIMIT.WINDOW_MS,
        },
        security: {
          inputValidation: true,
          rateLimiting: true,
          promptMaxLength: DEFAULTS.PROMPT.MAX_LENGTH,
        },
      };
    
      return {
        content: [
          {
            type: 'text',
            text: `🤖 AI BRIDGE SERVER INFO:\n\n${JSON.stringify(info, null, 2)}`,
          },
        ],
      };
    }
  • Input schema definition for the 'server_info' tool, which requires no parameters (empty properties).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • src/index.js:149-157 (registration)
    Registers the 'server_info' tool in the getAvailableTools() method, making it discoverable via ListToolsRequest.
    tools.push({
      name: 'server_info',
      description: 'Get server status and configuration',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    });
  • src/index.js:178-179 (registration)
    Registers the handler dispatch for 'server_info' tool calls in the CallToolRequestSchema handler switch statement.
    case 'server_info':
      return this.handleServerInfo();
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 of behavioral disclosure. It states the tool retrieves information ('Get'), implying a read-only operation, but doesn't disclose any behavioral traits such as authentication requirements, rate limits, error conditions, or what specific data is returned. This is a significant gap 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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration, making it easy for an agent to parse quickly.

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 doesn't explain what 'server status and configuration' entails (e.g., uptime, version, settings), how the data is returned, or any prerequisites. For a tool with no structured data support, this leaves critical gaps in understanding its behavior and output.

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, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters, as there's nothing to compensate for.

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 ('server status and configuration'). It distinguishes what information is retrieved, though it doesn't explicitly differentiate from sibling tools like 'ask_gemini' or 'ask_openai', which appear to serve different purposes (querying AI models vs. server diagnostics).

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 implies usage for checking server state but doesn't specify scenarios (e.g., troubleshooting, monitoring) or exclusions, leaving the agent to infer context without explicit direction.

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/fakoli/mcp-ai-bridge'

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