Skip to main content
Glama

get_agent_info

Retrieve detailed information about a specific ACP agent by providing its name. Part of the ACP-MCP-Server, this tool enables integration between ACP-based AI agents and MCP-compatible systems.

Instructions

Get detailed information about a specific ACP agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main execution handler for the 'get_agent_info' tool. It retrieves agent capabilities via the AgentDiscoveryTool or returns a 'not found' message if the agent is unknown. The @mcp.tool() decorator registers it with FastMCP using the function name as the tool name.
    @mcp.tool()
    async def get_agent_info(agent_name: str) -> str:
        """Get detailed information about a specific ACP agent"""
        capabilities = await discovery.get_agent_capabilities(agent_name)
        if capabilities:
            return str(capabilities)
        else:
            return f"Agent '{agent_name}' not found"
  • Invocation of register_discovery_tools during server initialization, which defines and registers the get_agent_info tool (and discover_acp_agents) to the FastMCP instance.
    register_discovery_tools(self.mcp, self.discovery)
  • Core helper function called by get_agent_info to fetch and format detailed capabilities information for a specific agent from the discovered agents cache.
    async def get_agent_capabilities(self, agent_name: str) -> Dict[str, Any]:
        """Get detailed capabilities of a specific agent"""
        # This could be extended to call a capabilities endpoint
        # For now, return basic info from discovery
        agent = self.discovered_agents.get(agent_name)
        if agent:
            return {
                "name": agent.name,
                "description": agent.description,
                "metadata": agent.metadata,
                "supports_streaming": True,  # ACP supports streaming
                "supports_multimodal": True,  # ACP supports multi-modal
                "interaction_modes": ["sync", "async", "stream"]
            }
        return {}
  • The registration function that defines both discovery tools using @mcp.tool() decorators and binds them to the provided FastMCP instance and AgentDiscoveryTool instance.
    def register_discovery_tools(mcp: FastMCP, discovery: AgentDiscoveryTool):
        
        @mcp.tool()
        async def discover_acp_agents() -> str:
            """Discover all available ACP agents and register them as resources"""
            agents = await discovery.discover_agents()
            
            result = {
                "discovered_count": len(agents),
                "agents": []
            }
            
            for agent in agents:
                agent_info = {
                    "name": agent.name,
                    "description": agent.description,
                    "resource_uri": discovery.get_mcp_resource_uri(agent.name),
                    "capabilities": await discovery.get_agent_capabilities(agent.name)
                }
                result["agents"].append(agent_info)
            
            return str(result)
        
        @mcp.tool()
        async def get_agent_info(agent_name: str) -> str:
            """Get detailed information about a specific ACP agent"""
            capabilities = await discovery.get_agent_capabilities(agent_name)
            if capabilities:
                return str(capabilities)
            else:
                return f"Agent '{agent_name}' not found"
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get'), but doesn't specify whether it requires authentication, has rate limits, what format the detailed information includes, or if there are any side effects. This leaves significant gaps for a tool that presumably fetches sensitive agent data.

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, focused sentence with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads the core purpose immediately.

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 the tool has an output schema (which should document return values), the description's main job is to clarify purpose and usage. While concise and clear on purpose, it lacks guidance on when to use it versus siblings and doesn't address behavioral aspects like authentication needs. For a 1-parameter read tool with output schema, this is minimally adequate but has clear gaps.

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

Parameters2/5

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

The input schema has 0% description coverage, so the description must compensate. It mentions 'specific ACP agent' which implies the 'agent_name' parameter identifies an agent, but doesn't clarify what constitutes a valid agent name, format expectations, or whether it's case-sensitive. This adds minimal semantic value beyond the schema's basic structure.

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 'detailed information about a specific ACP agent', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'discover_acp_agents' or 'get_server_info', which prevents 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 like 'discover_acp_agents' (which might list agents) or 'get_server_info' (which might provide server-level details). It also doesn't mention prerequisites or exclusions for usage.

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