condor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADMIN_KEY | Yes | Admin key for token minting | |
| ALLOWED_HOSTS | Yes | Comma-separated list of allowed hosts | |
| SESSION_SECRET | Yes | Secret for session HMAC | |
| TOOL_SIGNING_KEY | Yes | Signing key for tool manifest |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| catalog.searchC | Search the public product catalog by category. |
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 with other tools.
The single tool name 'catalog.search' follows a consistent noun.verb pattern, which is clear and predictable.
Having only one tool for a product catalog server is insufficient; a typical catalog server would need multiple tools for browsing, filtering, and retrieving details.
The tool set is severely incomplete for a product catalog: it only offers search by category, missing essential operations like listing categories, getting product details, or managing the catalog.