Skip to main content
Glama

get_info

Discover available capabilities, connected servers, and tool inventory for the Orchestrator MCP. Use this to gain insights and plan complex workflows effectively.

Instructions

System introspection - discover available capabilities, connected servers, and tool inventory. Use this to understand what the orchestrator can do before making complex requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic for the 'get_info' tool. It gathers server information, counts connected servers and tools, and returns formatted server capabilities.
    export async function handleGetInfo(orchestrator: OrchestratorManager) {
      try {
        const serverInfo = await orchestrator.getServerInfo();
        const connectedServers = Object.keys(serverInfo.servers).length;
        const totalTools = await orchestrator.getAllTools();
        
        const info = {
          name: 'Orchestrator MCP Server',
          version: '1.0.0',
          description: 'AI-enhanced MCP server orchestrator',
          connectedServers,
          totalTools: totalTools.length,
          servers: serverInfo.servers,
          capabilities: [
            'Multi-server orchestration',
            'AI-powered tool selection',
            'Intelligent workflow execution',
            'Tool usage tracking',
            'Intelligence layer analysis',
          ],
        };
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(info, null, 2),
            },
          ],
        };
      } catch (error) {
        logger.error('Failed to get server info:', error as Error);
        return {
          content: [
            {
              type: 'text',
              text: `Error getting server info: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
        };
      }
    }
  • The dispatcher function that registers the tool call handler and routes 'get_info' calls to the handleGetInfo function.
    export function setupToolCallHandler(
      server: Server,
      orchestrator: OrchestratorManager,
      aiOrchestrator: AIOrchestrator
    ): void {
      server.setRequestHandler(CallToolRequestSchema, async (request) => {
        const { name, arguments: args } = request.params;
        
        try {
          logger.info(`Handling tool call: ${name}`);
          
          // Route to streamlined tool handlers
          switch (name) {
            case 'ai_process':
              return handleAIProcess(args, aiOrchestrator);
    
            case 'get_info':
              return handleGetInfo(orchestrator);
    
            case 'ai_status':
              return handleAIStatus(aiOrchestrator);
    
            // Context engine tools removed
    
            default:
              // Try to delegate to connected servers
              return await orchestrator.callTool(name, args);
          }
        } catch (error) {
          logger.error(`Error handling tool call ${name}:`, error as Error);
          return createErrorResponse(error as Error);
        }
      });
    }
  • The schema definition for the 'get_info' tool provided in the listTools response, including name, description, and empty input schema.
    {
      name: 'get_info',
      description: 'System introspection - discover available capabilities, connected servers, and tool inventory. Use this to understand what the orchestrator can do before making complex requests.',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false,
        $schema: 'http://json-schema.org/draft-07/schema#',
      },
    },
Behavior3/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 describes the tool's function (introspection/discovery) but doesn't mention potential side effects, authentication requirements, rate limits, or what the return format looks like. The description adds value but lacks detailed behavioral context.

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 perfectly concise with two sentences that each earn their place: the first states what the tool does, and the second provides usage guidance. There's zero wasted text, and information is front-loaded appropriately.

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 (introspection with no parameters) and lack of annotations/output schema, the description is adequate but has clear gaps. It explains the purpose and usage context well, but doesn't describe what information is returned or any behavioral constraints, making it incomplete for full agent understanding.

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 with 100% schema description coverage, so the schema already fully documents the input (none required). The description doesn't need to add parameter information, and it appropriately focuses on the tool's purpose instead. Baseline 4 is appropriate for zero-parameter tools.

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 specific verbs ('discover available capabilities, connected servers, and tool inventory') and resources ('orchestrator'), making it immediately understandable. It doesn't explicitly differentiate from sibling tools (ai_process, ai_status), but the scope is well-defined.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('to understand what the orchestrator can do before making complex requests'), which is helpful guidance. However, it doesn't specify when NOT to use it or mention alternatives among the sibling tools, keeping it from a perfect score.

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/Phoenixrr2113/Orchestrator-MCP'

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