cortex-cloud-docs-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_cortex_docsB | Search Cortex Cloud documentation |
| search_cortex_api_docsC | Search Cortex Cloud API documentation |
| search_all_docsC | Search across all Cortex Cloud documentation sites. |
| index_cortex_docsA | Index Cortex Cloud documentation. Call this first before searching. |
| index_cortex_api_docsA | Index Cortex Cloud API documentation. Call this first before searching. |
| get_index_statusA | Check how many documents are currently cached. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Multiple tools have unclear boundaries and overlapping purposes. The distinction between 'index_cortex_api_docs' and 'index_cortex_docs' is ambiguous, as is the difference between 'search_cortex_api_docs' and 'search_cortex_docs'. This overlap could lead to misselection by agents, especially since the descriptions don't clearly differentiate the scopes or use cases for these similar tools.
All tool names follow a consistent verb_noun pattern with snake_case, such as 'get_index_status', 'index_cortex_api_docs', and 'search_all_docs'. This predictability makes the tool set easy to parse and understand, with no deviations in naming conventions across the six tools.
With 6 tools, the count is well-scoped for a documentation server focused on indexing and searching. Each tool appears to serve a distinct operational role, such as checking status, indexing specific doc types, and searching across various scopes, making the set appropriately sized without being overly complex or too sparse.
The tool surface covers core workflows for indexing and searching documentation, with tools for status checks, indexing different doc types, and searching across scopes. A minor gap exists in lacking explicit update or delete operations for cached documents, but agents can likely work around this by re-indexing, so the coverage is largely complete for the server's purpose.