Skip to main content
Glama

agora_get_user_orders

Retrieve all purchase orders for the current user on SearchAgora to view transaction history and manage past purchases.

Instructions

Get all orders for the current user.

Returns:
    A list of orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function implementing the 'agora_get_user_orders' tool logic. It is registered via the @mcp.tool() decorator. Calls get_agora().get_user_orders() and processes the response with handle_response.
    @mcp.tool()
    async def agora_get_user_orders() -> List[Dict]:
        """
        Get all orders for the current user.
        
        Returns:
            A list of orders.
        """
        response = get_agora().get_user_orders()
        return handle_response(response)
  • Helper function to lazily initialize and return the Agora client instance, used by the tool.
    def get_agora():
        """Get or create an Agora instance. 
        We want to create the class instance inside the tool, 
        so the init errors will bubble up to the tool and hence the MCP client instead of silently failing
        during the server creation.
        """
    
        return Agora()
  • Helper function to standardize responses from Agora API calls, returning status code and data or just the data.
    def handle_response(response):
        """
        Handle responses from Agora methods.
        """
        if hasattr(response, 'status_code'):
            # This is a raw response object
            try: return response.status_code, response.json()
            except: return response.status_code, response.text
        # This is already processed data (like a dictionary)
        return response
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'Get all orders for the current user' and mentions the return type, but lacks details on permissions, pagination, error handling, or rate limits. This is inadequate for a tool that likely accesses user data.

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 brief and front-loaded with the core purpose in the first sentence. The second sentence about returns is somewhat redundant but not wasteful. It could be more structured (e.g., combining both points), but it's efficient overall.

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?

Given no annotations and no output schema, the description is incomplete. It mentions a return type ('A list of orders') but doesn't specify order structure, error cases, or behavioral constraints. For a data retrieval tool, this leaves significant gaps for an agent.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but that's appropriate here. A baseline of 4 is given since the schema fully covers the lack of parameters.

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's purpose with a specific verb ('Get') and resource ('orders for the current user'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'agora_get_order' (singular vs. plural) or 'agora_search' (which might also retrieve orders), so it doesn't reach the highest 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. It doesn't mention siblings like 'agora_get_order' for single orders or 'agora_search' for filtered searches, leaving the agent to infer usage based on tool names 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/Fewsats/agora-mcp'

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