Skip to main content
Glama
pinecone-io

Pinecone Developer MCP

Official
by pinecone-io

search-docs

Search Pinecone documentation to find relevant information quickly by entering a query, simplifying access to specific technical details.

Instructions

Search Pinecone documentation for relevant information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe text to search for.

Implementation Reference

  • Handler function for the 'search-docs' tool. Connects to the Pinecone docs MCP server and calls its 'get_context' tool.
    server.tool('search-docs', INSTRUCTIONS, SCHEMA, async ({query}) => {
      const httpTransport = new StreamableHTTPClientTransport(new URL(DOCS_MCP_URL));
    
      const client = new Client({
        name: 'pinecone-docs',
        version: PINECONE_MCP_VERSION,
      });
    
      await client.connect(httpTransport);
    
      return (await client.callTool({
        name: 'get_context',
        arguments: {query},
      })) as SearchDocsResult;
    });
  • Instructions and Zod input schema for the 'search-docs' tool.
    const INSTRUCTIONS = 'Search Pinecone documentation for relevant information';
    
    const SCHEMA = {
      query: z.string().describe('The text to search for.'),
    };
  • Registration of the 'search-docs' tool via the addSearchDocsTool helper function called from docs/index.ts and ultimately from src/server.ts.
    export function addSearchDocsTool(server: McpServer) {
      server.tool('search-docs', INSTRUCTIONS, SCHEMA, async ({query}) => {
        const httpTransport = new StreamableHTTPClientTransport(new URL(DOCS_MCP_URL));
    
        const client = new Client({
          name: 'pinecone-docs',
          version: PINECONE_MCP_VERSION,
        });
    
        await client.connect(httpTransport);
    
        return (await client.callTool({
          name: 'get_context',
          arguments: {query},
        })) as SearchDocsResult;
      });
    }
  • Helper function addDocsTools that calls addSearchDocsTool to register the tool.
    export default async function addDocsTools(server: McpServer) {
      addSearchDocsTool(server);
    }
  • src/server.ts:45-46 (registration)
    Top-level call to addDocsTools during server setup, which triggers the tool registration.
    await addDocsTools(server);
    addDatabaseTools(server);
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 mentions searching but does not describe how results are returned, whether there are rate limits, authentication requirements, or any other behavioral traits. This leaves significant gaps for a search tool.

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 directly states the tool's purpose without any unnecessary words or fluff. It is appropriately sized and front-loaded, making it easy to understand 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 does not explain what the search returns, how results are structured, or any limitations, which is insufficient for a tool that performs information retrieval.

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?

The input schema has 100% description coverage, with the 'query' parameter clearly documented. The description does not add any additional meaning beyond what the schema provides, such as examples or formatting details, so it meets the baseline score of 3.

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 as searching Pinecone documentation for relevant information, which is a specific verb+resource combination. However, since there are no sibling tools mentioned, it cannot be evaluated for sibling differentiation, so it cannot achieve a perfect score of 5.

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, nor does it mention any prerequisites or exclusions. It simply states what the tool does without context for its 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

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/pinecone-io/pinecone-mcp'

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