Skip to main content
Glama
minuetai
by minuetai

get_recent_relationships

Retrieve a list of the most recently created agent relationships from the ERC-8004 graph. Specify a limit to control how many results are returned.

Instructions

Return the most recently created relationships.

Args: limit: Maximum number of relationships to return (default 20).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual tool handler function. Decorated with @mcp.tool(), it calls MinuetClient.list_relationships(), sorts by created_at descending, and returns up to `limit` relationships.
    @mcp.tool()
    async def get_recent_relationships(limit: int = 20) -> dict[str, Any]:
        """Return the most recently created relationships.
    
        Args:
            limit: Maximum number of relationships to return (default 20).
        """
        async with MinuetClient() as client:
            data = await client.list_relationships()
        relationships = data.get("relationships", [])
        relationships.sort(key=lambda r: r.get("created_at") or "", reverse=True)
        return {"count": min(limit, len(relationships)), "relationships": relationships[:limit]}
  • The @mcp.tool() decorator registers the function as an MCP tool named 'get_recent_relationships' (derived from the function name).
    @mcp.tool()
  • MinuetClient.list_relationships() — the underlying API call that fetches all relationships from /api/relationships, used by the handler.
    async def list_relationships(self) -> dict[str, Any]:
        return await self._get("/api/relationships")
  • Input schema: the function signature defines `limit: int = 20` as the only input parameter. Output is typed as dict[str, Any] returning count and relationships list.
    async def get_recent_relationships(limit: int = 20) -> dict[str, Any]:
        """Return the most recently created relationships.
    
        Args:
            limit: Maximum number of relationships to return (default 20).
  • Test verification that 'get_recent_relationships' is listed among the expected tool names in a smoke test.
        "get_recent_relationships",
    }
Behavior3/5

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

Annotations are absent, but the description implies a read-only operation (returning data). No side effects are mentioned, but for a simple retrieval, it is adequate. Could mention it is non-destructive.

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

Conciseness3/5

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

The description is very short, but lacks necessary context about the nature of 'relationships' and usage context. It is not overly verbose, but is underspecified.

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

Completeness2/5

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

While an output schema exists, the description does not explain what the tool returns beyond 'recently created relationships.' Missing context on what constitutes a relationship.

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?

Schema coverage is 0%, so the description should add value. It only repeats the default value of 'limit' (20) without explaining how the parameter interacts with the tool behavior.

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 states 'Return the most recently created relationships,' which clearly identifies the primary action and resource. However, 'relationships' could be more specific given sibling tools like 'get_agent_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 this tool vs alternatives such as 'get_agent_relationships' or 'get_relationship_graph'. The description does not differentiate its use case.

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