context-aware-mcp
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
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 |
|---|---|
| smart_api_callC | Intelligent API routing from natural language queries. Available services: os-order. Environments: local, qa. |
| fetch_swaggerC | Fetch OpenAPI spec for a service. Services: os-order |
| call_apiC | Direct API call to a specific service endpoint. |
| list_servicesC | List available services and their keywords |
| kafka_list_topicsA | List all Kafka topics. Optionally filter by pattern (regex). |
| kafka_describe_topicA | Get detailed metadata about a Kafka topic including partitions, replicas, and current offsets. |
| kafka_read_messagesB | Read recent messages from a Kafka topic. Useful for debugging event flows. |
| kafka_consumer_groupsC | List consumer groups and their offsets. Check consumer lag and group status. |
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 8 tools
The Kafka tools are clearly distinct, but the API tools overlap: smart_api_call and call_api both invoke APIs, and fetch_swagger/list_services are related discovery utilities. Descriptions partially clarify the difference between natural-language routing and direct calls, but an agent could still pick the wrong tool without additional context.
Most tools follow a verb_noun pattern (fetch_swagger, call_api, list_services) and the Kafka group consistently uses kafka_verb_noun. smart_api_call breaks the pattern because it is an adjective-noun phrase rather than a verb-initial name, but the inconsistency is minor.
Eight tools is well-scoped for a server covering both API discovery/invocation and Kafka inspection. Each tool addresses a distinct operational need without redundancy or bloat.
The API side covers service discovery, spec retrieval, and invocation, while the Kafka side covers listing, describing, reading, and consumer-group inspection. Minor gaps such as producing messages or managing offsets exist, but the surface seems complete for its apparent context-gathering purpose.