Skip to main content
Glama

get_server_info

Retrieve essential details about the ACP-MCP bridge server, enabling smooth integration between ACP-based AI agents and MCP-compatible tools like Claude Desktop.

Instructions

Get information about the ACP-MCP bridge server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_server_info' tool, decorated with @self.mcp.tool() for automatic registration with FastMCP. It returns a detailed JSON string containing server name, version, components, capabilities, and supported transports.
    @self.mcp.tool()
    async def get_server_info() -> str:
        """Get information about the ACP-MCP bridge server"""
        info = {
            "name": "ACP-MCP Bridge Server",
            "description": "Bridge between Agent Communication Protocol and Model Context Protocol",
            "version": "2.1.0",
            "components": [
                "Agent Discovery Tool",
                "Multi-Modal Message Bridge", 
                "Run Orchestrator",
                "Agent Router",
                "Interactive Manager"
            ],
            "acp_endpoint": self.discovery.acp_base_url,
            "supported_transports": [
                "stdio (default)",
                "sse (Server-Sent Events)",
                "streamable-http"
            ],
            "capabilities": [
                "Agent discovery and registration",
                "Multi-modal message conversion",
                "Sync/async/streaming execution",
                "Intelligent agent routing",
                "Interactive agent sessions",
                "Multiple transport protocol support"
            ]
        }
        return str(info)
  • The @self.mcp.tool() decorator registers the get_server_info function as an MCP tool.
    @self.mcp.tool()
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get information' implies a read-only operation, it doesn't specify what type of information is returned, whether there are authentication requirements, rate limits, or any side effects. For a tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's perfectly front-loaded and wastes no space, making it ideal for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the tool has zero parameters, 100% schema coverage, and an output schema exists, the description doesn't need to cover parameters or return values. However, with no annotations and multiple sibling tools that might overlap in function, the description should provide more context about what specific information is retrieved to help distinguish it from alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The description appropriately focuses on the tool's purpose rather than parameter details, earning a baseline score of 4 for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('information about the ACP-MCP bridge server'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'get_agent_info' or 'discover_acp_agents' which might also retrieve server-related information, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_agent_info' and 'discover_acp_agents' that might retrieve related information, there's no indication of what distinguishes this tool's scope or when it's the appropriate choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GongRzhe/ACP-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server