Skip to main content
Glama

agora_get_order

Retrieve specific order details from Agora by providing the order ID to access purchase information and status.

Instructions

Get details for a specific order in Agora.

Args:
    order_id: The order ID.
    
Returns:
    The order details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes

Implementation Reference

  • Implements the agora_get_order tool: an async function decorated with @mcp.tool() that retrieves order details from the Agora client using the provided order_id and processes the response using handle_response.
    @mcp.tool()
    async def agora_get_order(order_id: str) -> Dict:
        """
        Get details for a specific order in Agora.
        
        Args:
            order_id: The order ID.
            
        Returns:
            The order details.
        """
        response = get_agora().get_order(order_id=order_id)
        return handle_response(response)
  • Helper function to lazily initialize and return the Agora client instance inside tool execution to handle initialization errors gracefully.
    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, distinguishing between raw HTTP responses and processed 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 this is a read operation ('Get'), implying it's non-destructive, but doesn't cover critical aspects like authentication requirements, error handling, rate limits, or what happens if the order ID is invalid. The description lacks depth for a tool that likely interacts with sensitive order 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 appropriately sized and front-loaded with the core purpose in the first sentence. The 'Args' and 'Returns' sections add structure, though they could be more detailed. There's no wasted text, but it risks being too sparse for a tool with no annotations or output schema.

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, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain what 'order details' include (e.g., items, status, timestamps), error scenarios, or system constraints. For a tool that retrieves potentially complex order data, this leaves significant gaps for an AI agent to operate effectively.

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 schema description coverage is 0%, so the description must compensate. It adds minimal semantics by naming 'order_id' and stating it's 'The order ID', but doesn't explain format, length, or source (e.g., from a previous order list). This provides basic context but falls short of fully documenting the parameter's meaning and constraints.

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 'Get details for a specific order in Agora', specifying the verb 'Get' and resource 'order details'. It distinguishes from siblings like 'agora_get_user_orders' (which lists multiple orders) by focusing on a single order, but doesn't explicitly mention this distinction.

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 prerequisites (e.g., needing an order ID), exclusions, or comparisons to siblings like 'agora_get_user_orders' for listing orders or 'agora_search' for broader queries.

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