Skip to main content
Glama
Fewsats

Agora MCP

by Fewsats
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
agora_searchB
Search for products matching the query in Agora.

Args:
    q: The search query.
    count: The number of products to return per page.
    page: The page number.
    price_min: The minimum price. Optional
    price_max: The maximum price. Optional
    sort: The sort field: price:relevance.
    order: The sort order: asc or desc.
    
Returns:
    The search results.
agora_get_product_detailB
Get details for a specific product in Agora.

Args:
    slug: The product slug, it usually looks something like 'royal-blue-waxed-shoe-laces-6f2049ef-0d08-4a79-8937-025bb596092f-1718242165922'
    
Returns:
    The product details.
agora_get_payment_offersA
Get the payment offers for a product in Agora. Some products do not have variants, in such cases use the product_id as variant_id too.
Before calling this tool, check if the user has already provided the shipping address and user information. 
Otherwise, ask the user for the shipping address and user information.

If the user does not provide an `addressName`, use the `firstname` and `lastname` to populate it.
Args:
    slug: The product slug.
    product_id: The product ID as str delimited by escaped double quotes
    variant_id: The product variant ID as str delimited by escaped double quotes
    quantity: The quantity to purchase.
    shipping_address: The shipping address.
    user: The user information.
    
Example:
    product_id = "\"1234567890\""
    variant_id = "\"1234567890\""
    shipping_address = {
        "addressName": "John Doe",
        "addressFirst": "123 Main St",
        "city": "New York",
        "state": "NY",
        "country": "US",
        "zipCode": "10001"
    }
    
    user = {
        "firstname": "John",
        "lastname": "Doe",
        "email": "john@example.com",
    }
    
Returns:
    L402 offer that can be paid by L402-compatible clients.
agora_get_orderC
Get details for a specific order in Agora.

Args:
    order_id: The order ID.
    
Returns:
    The order details.
agora_get_user_ordersB
Get all orders for the current user.

Returns:
    A list of orders.
agora_get_user_infoB
Get the current user's profile and shipping addresses in Agora.

Returns:
    Dict containing user profile info (firstname, lastname, email) and list of shipping addresses

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting different resources: get_order, get_payment_offers, get_product_detail, get_user_info, get_user_orders, and search. There is no overlap in functionality, making it easy for an agent to select the right tool for each task.

Naming Consistency5/5

All tool names follow a consistent 'agora_verb_noun' pattern using snake_case, such as 'agora_get_order' and 'agora_search'. This predictability enhances readability and reduces confusion when navigating the tool set.

Tool Count5/5

With 6 tools, the set is well-scoped for an e-commerce platform like Agora, covering core operations like product search, details, orders, payments, and user management. Each tool serves a distinct and necessary function without being excessive or insufficient.

Completeness4/5

The tool set provides strong coverage for browsing, ordering, and user management, but lacks update or delete operations (e.g., updating user info or canceling orders). Agents can work around these gaps, but the absence limits full lifecycle management in the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources