A
license-
qualityC
maintenancePer-call billing and metering proxy for MCP tool servers. Providers set pricing via the open MCP Billing Spec (MIT), consumers pay through Stripe Connect with signed receipts and SLA monitoring.
MIT
clawmerchants-mcp-gateway
Server Details
MCP Gateway: wrap any MCP server with cold-start retries, uptime SLA, and per-execution MPP billing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 4.2/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools have clearly distinct purposes: get_asset retrieves details for a specific asset including payment instructions, while list_assets provides an overview of all available assets in the marketplace. There is no overlap or ambiguity between them.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern (get_asset and list_assets), using snake_case and clear action verbs that align with their functions. The naming is predictable and readable throughout.
Tool Count2/5
With only two tools, the server feels thin for a marketplace gateway that presumably involves purchasing assets. Key operations like initiating purchases, managing transactions, or accessing purchased data are missing, making the toolset insufficient for the apparent scope.
Completeness2/5
The toolset is severely incomplete for a marketplace gateway. While it covers listing and getting asset details, there is no tool for actually purchasing assets (e.g., a buy_asset or purchase_asset tool), nor for handling post-payment data retrieval or transaction management, leaving significant gaps in the workflow.
Available Tools
2 toolsget_assetAInspect
Get details for a specific asset including its x402 payment endpoint. To purchase: send a GET request to the payment_url — you will receive an HTTP 402 response with Base L2 USDC payment instructions. Pay the invoice, then resend the request with the x-payment header to receive the data.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asset_id | Yes | The asset ID (e.g. defi-yields-live, security-intel-live) |
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the x402 payment endpoint and describes the purchase protocol step-by-step (HTTP 402, Base L2 USDC, x-payment header), which is rich behavioral context. It does not explicitly state read-only status or discuss auth/rate limits, but the operation is clearly a read by name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, with the purpose front-loaded. The second sentence is detailed but directly relevant to using the returned endpoint. No redundant or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having only one parameter and no output schema, the description thoroughly explains the key output (payment endpoint) and the complete purchase workflow. This gives an agent all necessary context to use the tool correctly.
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?
Schema coverage is 100% for the single asset_id parameter, and the description adds no additional meaning or examples beyond what the schema already provides. Baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Get details for a specific asset' with a specific verb and resource. The inclusion of 'specific' distinguishes it from sibling list_assets, which enumerates assets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a clear usage scenario by explaining the payment flow for purchasing an asset. Implicitly contrasts with list_assets by saying 'specific asset', but does not explicitly name the alternative or state when not to use the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_assetsAInspect
List available data assets, skills, and tools in the ClawMerchants marketplace. Each asset is purchasable via x402 micropayment in USDC on Base L2. Returns asset IDs, names, prices, categories, and descriptions.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results to return (default: 20) | |
| search | No | Search by name or description | |
| category | No | Filter by category: crypto, security, developer, market-data, ai-ml, knowledge, real-time, agent-skills, agent-tools, other |
Tool Definition Quality
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the transparency burden. It discloses that the tool returns asset IDs, names, prices, categories, and descriptions, and that assets are purchasable via x402. However, it omits any statement about read-only nature, authentication requirements, pagination behavior, or rate limits, which would improve operational clarity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the primary action and resource, then adds payment context and return fields. Every sentence earns its place with no redundant phrasing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a low-complexity list tool with three optional parameters and no output schema. The description covers return fields, marketplace context, and payment mechanism, which is sufficient for an agent to invoke it correctly. A minor gap is the lack of explicit sibling guidance, but overall completeness is strong.
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 provides 100% coverage for all three parameters (limit, search, category) with descriptions, so the description does not need to repeat them. It adds no additional parameter semantics beyond what the schema already provides, which lands at the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and identifies the exact resource ('available data assets, skills, and tools in the ClawMerchants marketplace'). It clearly differentiates from sibling tool 'get_asset' by implying this is the browsing/list operation versus a single-asset fetch.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context: this lists marketplace assets and notes they are purchasable via x402 micropayment. However, it does not explicitly state when to prefer this over 'get_asset' or provide exclusion criteria, so it stops short of full guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceMCP Gateway that aggregates multiple upstream MCP servers into a single endpoint with persistent connections, tool registry, and authentication.212MIT
- Alicense-qualityDmaintenanceGateway MCP Server - Route MCP requests intelligently to multiple backend servers.3MIT
- Alicense-qualityBmaintenanceA universal MCP gateway that aggregates multiple MCP servers into a single endpoint, providing features like hot-reload, auto-healing, and a hook system for request/response mutation.1MIT