Skip to main content
Glama
minuetai
by minuetai

get_recent_relationships

Retrieve the most recently created relationships from the Minuet relationship graph. Specify a limit to control how many 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 handler function for the 'get_recent_relationships' MCP tool. It calls the MinuetClient.list_relationships() API, sorts the results by 'created_at' descending, and returns up to `limit` relationships.
    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 input schema is defined via the function signature (limit: int = 20), which FastMCP converts to a JSON Schema automatically. The return type is dict[str, Any].
    async def get_recent_relationships(limit: int = 20) -> dict[str, Any]:
  • The tool is registered via the @mcp.tool() decorator on the async function. `mcp` is a FastMCP instance defined on line 16 as FastMCP("minuet-mcp").
    @mcp.tool()
  • The helper method list_relationships() on the MinuetClient class, which is called by the handler. It makes a GET request to /api/relationships on the Minuet API.
    async def list_relationships(self) -> dict[str, Any]:
        return await self._get("/api/relationships")
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states it returns recent relationships, but does not specify ordering, safety (read-only vs destructive), or any side effects. This is insufficient for reliable agent decision-making.

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

Conciseness4/5

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

The description is short and front-loaded with the main purpose. However, it uses a structured 'Args' format that could be streamlined. It is efficient but not maximally concise.

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's simplicity and the presence of an output schema (not shown), the description is minimally complete. It lacks explanation of what a 'relationship' is and any prerequisites. For a simple list tool, this is adequate but leaves gaps.

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

Parameters3/5

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

The description adds meaning to the 'limit' parameter beyond the schema (which only provides default and type), stating it controls the maximum number of relationships. However, with 0% schema coverage, it should provide more detail, such as range constraints or behavior if omitted.

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 tool returns 'the most recently created relationships', which is a specific verb and resource. However, it does not differentiate from sibling tools like get_agent_relationships or search_agents, which could also return relationship data.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts, or exclusions, leaving the agent to infer usage from name alone.

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