acme-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP1_SERVER_PATH | Yes | Absolute path to the MCP 1 (vector store) server. MCP 2 uses this to spawn MCP 1 as a subprocess. | |
| AZURE_OPENAI_API_KEY | Yes | The API key for Azure OpenAI or Azure AI Foundry. | |
| AZURE_OPENAI_ENDPOINT | Yes | The Azure OpenAI or Azure AI Foundry endpoint URL. | |
| AZURE_OPENAI_CHAT_DEPLOYMENT | Yes | The deployment name for the chat model (e.g., GPT-4) in Azure AI Foundry. | |
| AZURE_OPENAI_EMBEDDING_DEPLOYMENT | Yes | The deployment name for the embedding model in Azure OpenAI. |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| askC | Ask a question about Acme Robotics. The agent will decompose the question, retrieve relevant information from the knowledge base, and synthesize a final answer. |
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 ambiguity or overlap between tools. The single tool 'ask' has a clearly defined and distinct purpose, making it impossible for an agent to misselect between tools.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'ask' follows a simple verb pattern, which is appropriate for its function.
One tool is generally too few for a server's purpose unless it is a trivial or highly specialized single-function server. For a domain like 'Acme Robotics', a single 'ask' tool feels thin and under-scoped, limiting the agent's ability to perform diverse operations.
Inferring the domain as 'Acme Robotics', the tool surface is severely incomplete. A single 'ask' tool provides no CRUD/lifecycle coverage, no ability to interact with robotics systems (e.g., control, monitor, configure), and leaves significant gaps that will cause agent failures in practical scenarios.