Skip to main content
Glama
Pinecone Developer MCP

Pinecone Developer MCP

Official
by pinecone-io

Search Pinecone Documentation

search-docs
Read-only

Search official Pinecone documentation for relevant information before writing Pinecone code or explaining Pinecone behavior, so answers rely on documented facts instead of assumptions.

Instructions

Search the official Pinecone documentation for relevant information. Use this before writing Pinecone code or explaining Pinecone behavior, rather than relying on assumptions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search-docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe text to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It adds that the source is the official documentation (implying authoritative, current results), but says nothing about result format, number of hits, or freshness. Adequate but thin beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what it does and followed by when to call it. Every sentence earns its place, though it is slightly under-specified rather than maximally informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with no output schema, the definition covers purpose and timing well. The only gap is that it doesn't hint at what comes back (snippets, links), which would help an agent plan follow-up calls.

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?

Single required parameter 'query' with 100% schema coverage, so the schema already fully documents it. The description adds no guidance on query phrasing, natural-language vs keyword, or scoping. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (official Pinecone documentation), which cleanly separates it from every sibling (indexes, records, documents, reranking). An agent can tell this is the documentation-lookup tool without opening the schema.

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?

Gives explicit timing guidance: use it before writing Pinecone code or explaining Pinecone behavior, and explicitly warns against relying on assumptions. It stops short of naming when NOT to use it or which sibling to prefer for data queries, but the exclusion is largely implicit given the siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.