Acemcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOKEN | No | Your authentication token for the API | |
| BASE_URL | No | The base URL for the API endpoint (e.g., https://api.example.com) | |
| BATCH_SIZE | No | The batch size for uploading files | 10 |
| MAX_LINES_PER_BLOB | No | Maximum number of lines per blob when splitting large files | 800 |
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_contextA | Search for relevant code context based on a query within a specific project. This tool automatically performs incremental indexing before searching, ensuring results are always up-to-date. Returns formatted text snippets from the codebase that are semantically related to your query. Supports cross-platform paths including Windows WSL. |
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 with other tools. The tool's purpose is clearly defined as searching for code context, making it impossible for an agent to misselect between multiple options.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The tool name 'search_context' follows a clear verb_noun pattern, which would be consistent if more tools were added.
One tool is too few for most server purposes, as it severely limits functionality and scope. While the tool is well-described for code context searching, a single tool feels thin and incomplete for broader operations, suggesting an extreme mismatch in tool count for typical server needs.
The server appears focused on code context searching, but with only one tool, there are significant gaps in coverage. For example, there are no tools for creating, updating, or managing code context, or for other related operations like indexing control or project management, leading to a severely incomplete surface.