Skip to main content
Glama
minuetai
by minuetai

get_agent

Retrieve comprehensive details and relationships for any ERC-8004 agent using its chain-specific identifier.

Instructions

Fetch full details for a specific agent, including its Minuet relationships.

Args: agent_id: Canonical identifier in the form chainId:agentId (e.g. 1:6817 for Ethereum mainnet agent 6817).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_agent'. Decorated with @mcp.tool(), it creates a MinuetClient and delegates to the client's get_agent method.
    @mcp.tool()
    async def get_agent(agent_id: str) -> dict[str, Any]:
        """Fetch full details for a specific agent, including its Minuet relationships.
    
        Args:
            agent_id: Canonical identifier in the form `chainId:agentId`
                (e.g. `1:6817` for Ethereum mainnet agent 6817).
        """
        async with MinuetClient() as client:
            return await client.get_agent(agent_id)
  • Input schema for get_agent: accepts a single 'agent_id' string parameter documented in the docstring.
    Args:
        agent_id: Canonical identifier in the form `chainId:agentId`
            (e.g. `1:6817` for Ethereum mainnet agent 6817).
  • Tool registration via the @mcp.tool() decorator on FastMCP instance 'mcp' (line 16).
    @mcp.tool()
    async def search_agents(query: str | None = None, limit: int = 25) -> dict[str, Any]:
        """Search indexed ERC-8004 agents.
    
        Args:
            query: Optional substring to match against agent name.
            limit: Maximum number of agents to return (default 25).
        """
        async with MinuetClient() as client:
            data = await client.list_agents(name=query, limit=limit)
        agents = data.get("agents", [])[:limit]
        return {"count": len(agents), "agents": agents}
    
    
    @mcp.tool()
  • The MinuetClient helper method that makes the actual HTTP GET request to /api/agent/{agent_id}.
    async def get_agent(self, agent_id: str) -> dict[str, Any]:
        return await self._get(f"/api/agent/{agent_id}")
Behavior3/5

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

No annotations provided, so description carries full burden. States 'Fetch', implying read-only, but no mention of authentication, rate limits, or response characteristics. Adequate but minimal.

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?

Two concise sentences plus an ARGS section. Every sentence adds value; no filler. Front-loaded with purpose.

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

Completeness4/5

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

Given one parameter and an output schema, description covers the key format. Could mention that relationships are embedded in the response, but adequately complete for this simple fetch tool.

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?

Schema description coverage is 0%, so description must compensate. It adds format 'chainId:agentId' with example, which is valuable beyond the schema's type-only definition.

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

Purpose5/5

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

Explicit verb 'Fetch' and resource 'full details for a specific agent' with clear scope 'including its Minuet relationships'. This distinguishes it from sibling get_agent_relationships, which likely returns only relationships.

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?

No guidance on when to use or when to choose alternatives. Provides the required parameter format but no context on appropriate use cases.

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

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/minuetai/minuet-mcp'

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