Skip to main content
Glama
minuetai
by minuetai

get_owner_ecosystems

Find wallet addresses that operate multiple connected agents. Identifies ecosystems where a single owner has at least two named agents with relationships, enabling discovery of multi-agent teams.

Instructions

Return owners who operate multiple connected agents.

An "ecosystem" is a single wallet address with 2+ named agents that have at least one relationship. Useful for finding multi-agent teams.

Args: limit: Maximum number of ecosystems to return (default 10).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'get_owner_ecosystems' tool. Decorated with @mcp.tool(), it creates a MinuetClient, calls client.get_clusters(), extracts the 'ecosystems' key from the response (applying the limit), and returns a dict with count and ecosystems list.
    @mcp.tool()
    async def get_owner_ecosystems(limit: int = 10) -> dict[str, Any]:
        """Return owners who operate multiple connected agents.
    
        An "ecosystem" is a single wallet address with 2+ named agents that
        have at least one relationship. Useful for finding multi-agent teams.
    
        Args:
            limit: Maximum number of ecosystems to return (default 10).
        """
        async with MinuetClient() as client:
            data = await client.get_clusters()
        ecosystems = data.get("ecosystems", [])[:limit]
        return {"count": len(ecosystems), "ecosystems": ecosystems}
  • The tool is registered via the @mcp.tool() decorator on line 86, which registers 'get_owner_ecosystems' as an MCP tool with the FastMCP server instance 'mcp' (defined on line 16).
    @mcp.tool()
  • Helper method 'get_clusters' on MinuetClient. This is the underlying API call used by get_owner_ecosystems — it hits GET /api/relationships/clusters and returns the JSON response containing both 'hubs' and 'ecosystems' data.
    async def get_clusters(self) -> dict[str, Any]:
        return await self._get("/api/relationships/clusters")
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool returns owners (wallet addresses) with at least 2 named agents that have a relationship, and includes a limit parameter. It does not cover auth or rate limits, but for a simple read operation, the behavior is transparent enough.

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 succinct: a one-sentence purpose, a definition of the key term, and a clear parameter description. No unnecessary words, and the structure is front-loaded with the primary action.

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

Completeness5/5

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

Given the tool's simplicity (one optional parameter, output schema exists), the description fully specifies what the tool returns and the condition for an ecosystem. It is complete for an agent to invoke correctly.

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

Parameters5/5

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

The only parameter 'limit' has a default in the schema, but the description adds the semantic meaning 'Maximum number of ecosystems to return', which fully clarifies its role. Schema description coverage is 0%, so the description compensates completely.

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?

The description clearly states that the tool returns owners with multiple connected agents, defines an 'ecosystem', and differentiates it from siblings like get_agent or get_agent_relationships by focusing on owners with multiple connected agents.

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

Usage Guidelines4/5

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

The description notes it is useful for finding multi-agent teams, providing context on when to use it. It does not explicitly mention alternatives or when not to use, but the utility is clear enough for an agent to select it appropriately.

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