Contextual MCP Server
OfficialServer 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 |
|---|---|
| queryC | An enterprise search tool that can answer questions about any sort of knowledge base |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'query' has a clearly distinct and singular purpose, making disambiguation perfect.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'query' follows a simple, clear pattern with no deviations to assess.
A single tool for an 'enterprise search' server feels thin and under-scoped. While it might handle basic queries, it lacks complementary tools for managing or refining searches, making the count inappropriate for the apparent domain.
The tool surface is severely incomplete for enterprise search. It only provides a query function, missing essential operations like indexing, filtering, updating knowledge bases, or handling search results, which are critical for such a domain.