Skip to main content
Glama
damian-pramparo

Enterprise Code Search MCP Server

get_embedding_provider_info

Retrieve details about the current AI embedding provider configured for semantic code search, including model information and capabilities.

Instructions

Get information about the current embedding provider

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function implementing the 'get_embedding_provider_info' tool. It generates a markdown report on the current embedding provider (OpenAI or Ollama), including configuration details, API key status (for OpenAI), host/model (for Ollama), and connection test with available models list.
    async getEmbeddingProviderInfo() {
      let info = `# Embedding Provider Information\n\n`;
      info += `**Current Provider:** ${this.config.embedding_provider}\n\n`;
      
      if (this.config.embedding_provider === 'openai') {
        info += `## OpenAI Configuration\n`;
        info += `- **Model:** ${this.config.openai_model}\n`;
        info += `- **API Key:** ${this.config.openai_api_key ? 'Configured ✓' : 'Not configured ✗'}\n`;
      } else {
        info += `## Ollama Configuration\n`;
        info += `- **Host:** ${this.config.ollama_host}\n`;
        info += `- **Model:** ${this.config.ollama_model}\n`;
        
        try {
          const response = await fetch(`${this.config.ollama_host}/api/tags`);
          if (response.ok) {
            const data = await response.json();
            const models = data.models?.map((m: any) => m.name) || [];
            info += `- **Connection:** ✓ Connected\n`;
            info += `- **Available Models:** ${models.join(', ') || 'None'}\n`;
          } else {
            info += `- **Connection:** ✗ Failed to connect\n`;
          }
        } catch (error) {
          info += `- **Connection:** ✗ Error connecting\n`;
        }
      }
      
      return {
        content: [
          { type: "text", text: info }
        ]
      };
    }
  • src/index.ts:95-102 (registration)
    Registration of the tool in the stdio MCP server (index.ts), including name, description, and empty input schema. Dispatched to this.getEmbeddingProviderInfo() in the CallToolRequestSchema handler.
    {
      name: "get_embedding_provider_info",
      description: "Get information about the current embedding provider",
      inputSchema: {
        type: "object",
        properties: {}
      }
    }
  • Registration of the tool in the HTTP MCP server (http-server.ts), including name, description, and empty input schema. Dispatched to this.getEmbeddingProviderInfo() in the callTool method.
    {
      name: "get_embedding_provider_info",
      description: "Get information about the current embedding provider",
      inputSchema: {
        type: "object",
        properties: {}
      }
    }
  • Input schema definition for the tool (empty object, no parameters required).
      inputSchema: {
        type: "object",
        properties: {}
      }
    }
  • Input schema definition for the tool (empty object, no parameters required).
    inputSchema: {
      type: "object",
      properties: {}
    }
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 only states what the tool does without revealing any traits like whether it's read-only, if it requires authentication, what data it returns (e.g., provider name, configuration details), or potential errors. This leaves significant gaps in understanding its behavior.

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, clear sentence that directly states the tool's purpose without any unnecessary words or fluff. It's front-loaded with the key action ('Get information'), making it easy to parse quickly. Every word earns its place, resulting in an efficient and well-structured description.

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 complexity of a tool that retrieves provider information, the description is incomplete. With no annotations and no output schema, it fails to explain what information is returned (e.g., provider type, settings, status) or any behavioral aspects like error handling. This makes it inadequate for users to fully understand the tool's functionality 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 schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. This meets the baseline for tools with no parameters, as it doesn't mislead or omit necessary information.

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 ('information about the current embedding provider'), making it easy to understand what it does. However, it doesn't differentiate from sibling tools like 'list_indexed_projects' or 'search_codebase', which are unrelated to embedding providers, so it doesn't fully distinguish itself in context.

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 doesn't mention any prerequisites, such as needing an embedding provider to be configured, or specify use cases like checking provider settings before performing operations. Without this context, users might struggle to determine its appropriate application.

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/damian-pramparo/semantic-context-mcp'

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