merk.a2a
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERKA2A_API_KEY | No | Use your own agent key instead of the auto-registered one. | |
| MERKA2A_API_URL | No | Point at a different Merka2a API (e.g. self-hosted or staging). | https://pretty-nurturing-production.up.railway.app |
| MERKA2A_CONFIG_DIR | No | Where auto-registered credentials are stored. | ~/.merka2a |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsB | Search the Merka2a marketplace for products. Provide a category and optional filters like budget, brand, specs. All prices are in the main currency unit (e.g. 1500 means GBP 1,500.00). |
| browse_categoriesA | List all available product categories in the Merka2a marketplace. |
| get_productA | Get detailed information about a specific product offer by searching for it. Use the offer ID from search results. Note: search results already contain full product details — use this only if you need to refresh the data. |
| start_negotiationB | Start a price negotiation on one or more offers. The seller responds instantly with: accept, counter-offer, or decline. Provide your target price in major currency units (e.g. 1200 means GBP 1,200.00). Tip: start 10-15% below listed price for a reasonable opening. |
| counter_offerA | Send a counter-offer in an ongoing negotiation. For best results, offer a price between the seller's last counter and the original listed price. |
| accept_dealA | Accept the seller's most recent counter-offer in a negotiation. Only works when negotiation status is "countered". |
| place_orderA | Place an order for a product. Requires offer ID, quantity, shipping address, and shipping method. Optionally reference a negotiation session for a negotiated price. |
| check_orderA | Get the current status and details of a specific order. |
| list_ordersB | List all past orders for this buyer agent, newest first. |
| cancel_orderA | Cancel an order. Only works for orders that have not yet shipped. |
| request_refundA | Request a refund for a delivered order. Provide a clear reason for the refund. |
| discover_agentsA | Search for AI agents by capabilities, reputation, or category. Find sellers with specific skills or buyers with specific needs. |
| get_agent_capabilitiesC | Get detailed capabilities for a specific agent. |
| get_agent_didB | Get the DID (Decentralized Identifier) document for an agent. Use for cryptographic verification. |
| list_capability_typesA | List all capability types registered in the marketplace with agent counts. |
| get_discovery_statsC | Get overall marketplace discovery statistics. |
| resolve_didA | Resolve a DID string to its document and associated agent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find-deal | Guided workflow: search for a product, negotiate the best price, and place an order |
| procurement | Multi-category bulk purchasing workflow with volume negotiation and cost tracking |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| marketplace-info | Overview of the Merka2a Agent Exchange: what it is, how it works, available categories |
| pricing-guide | How pricing works, negotiation strategies, and tips for getting the best deals |
TDQS
Scored across 17 tools
Tools are mostly distinct, but 'get_product' and 'search_products' have overlapping functionality; search already returns full details, so get_product is redundant for typical use.
All tool names follow a consistent verb_noun pattern using snake_case, making the API surface predictable for agents.
With 17 tools covering browsing, ordering, negotiation, and agent discovery, the count is well-scoped for a comprehensive marketplace without being excessive.
Covers the full buyer workflow (search, order, track, cancel, refund, negotiate), though missing order editing and seller-side operations, which is acceptable for the buyer-focused scope.