ACP-MCP-Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_server_infoB | Get information about the ACP-MCP bridge server |
| discover_acp_agentsB | Discover all available ACP agents and register them as resources |
| get_agent_infoC | Get detailed information about a specific ACP agent |
| convert_acp_messageB | Convert ACP message format to MCP-compatible format |
| analyze_message_contentC | Analyze the content types and structure of an ACP message |
| run_acp_agentC | Execute an ACP agent with specified mode |
| get_async_run_resultC | Get the result of an asynchronous run |
| list_active_runsB | List all active runs |
| smart_route_requestC | Intelligently route a request to the best ACP agent |
| add_routing_ruleC | Add a new routing rule to a strategy |
| list_routing_strategiesB | List all available routing strategies and their rules |
| test_routingA | Test routing without executing - shows which agent would be selected |
| start_interactive_agentC | Start an interactive ACP agent that may require user input |
| provide_user_inputC | Provide user input to resume a waiting interactive agent |
| list_pending_interactionsB | List all pending interactive agents waiting for input |
| cancel_interactionC | Cancel a pending interactive agent |
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 16 tools
Most tools have distinct purposes, but there is some potential overlap between 'smart_route_request' and 'test_routing' as both involve routing decisions, which could cause confusion. The other tools are clearly differentiated by their specific actions on agents, runs, interactions, or routing components.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as 'add_routing_rule', 'analyze_message_content', and 'run_acp_agent'. This uniformity makes the tool set predictable and easy to navigate.
With 16 tools, the count is slightly high but reasonable for an ACP-MCP bridge server covering discovery, routing, execution, and interaction management. It might feel a bit heavy, but each tool appears to serve a specific function in this domain.
The tool set provides comprehensive coverage for the ACP agent domain, including agent discovery, information retrieval, execution (synchronous and asynchronous), routing management, interaction handling, and message conversion. There are no obvious gaps, supporting full lifecycle management.