Skip to main content
Glama
clarkemn

prisma-cloud-docs-mcp-server

index_prisma_docs

Index Prisma Cloud documentation to enable search functionality. Call this tool first to prepare documentation for queries.

Instructions

Index Prisma Cloud documentation. Call this first before searching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_pagesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the index_prisma_docs tool, registered via @mcp.tool() decorator. Indexes Prisma Cloud documentation pages using the indexer and returns the number of pages indexed.
    @mcp.tool()
    async def index_prisma_docs(max_pages: int = 50) -> str:
        """Index Prisma Cloud documentation. Call this first before searching."""
        pages_indexed = await indexer.index_site('prisma_cloud', max_pages)
        return f"Indexed {pages_indexed} pages from Prisma Cloud documentation"
  • Handler function for the index_prisma_docs tool, registered via @mcp.tool() decorator. Indexes Prisma Cloud documentation pages using the indexer and returns the number of pages indexed.
    @mcp.tool()
    async def index_prisma_docs(max_pages: int = 50) -> str:
        """Index Prisma Cloud documentation. Call this first before searching."""
        pages_indexed = await indexer.index_site('prisma_cloud', max_pages)
        return f"Indexed {pages_indexed} pages from Prisma Cloud documentation"
Behavior2/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. While it mentions that this should be called 'first before searching' (implying it's a setup/preparation step), it doesn't describe what 'indexing' actually does (e.g., whether it crawls/scrapes documentation, builds a search index, stores data locally/remotely), what happens if called multiple times, or any performance/rate limit considerations.

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 extremely concise with just two short sentences that each serve a clear purpose: stating the action and providing usage guidance. There's no wasted language or unnecessary elaboration.

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 that there's an output schema (which presumably describes the return values), the description doesn't need to explain return values. However, for an indexing tool with no annotations and a parameter that lacks explanation, the description should provide more context about what indexing entails and how the parameter affects the operation to be truly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 1 parameter with 0% description coverage, so the description must compensate. The description provides no information about the 'max_pages' parameter - it doesn't explain what pages are being indexed, what happens when the limit is reached, or typical values. This leaves the parameter's purpose and usage unclear.

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 action ('Index') and resource ('Prisma Cloud documentation'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from its sibling 'index_prisma_api_docs', which appears to serve a similar indexing function for API docs specifically.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool ('Call this first before searching'), which clearly distinguishes it from the search-related sibling tools. This tells the agent the proper sequence of operations in the workflow.

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/clarkemn/prisma-cloud-docs-mcp-server'

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