useful-data-source-for-agents-doing-product-price-sdk
Server Details
Semantic product search over Singapore e-commerce, ranked by an auditable entropy-based value-score
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- nexus-mcp-infra/useful-data-source-for-agents-doing-product-price-sdk
- GitHub Stars
- 0
- Server Listing
- buywhere-singapore-value-intelligence
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
2 toolsnexus_useful_data_source_for_agents_doing_prod_fetch_buywhere_vendor_price_distributionAInspect
Given a BuyWhere product identifier, returns the full cross-vendor price distribution in SGD along with the Shannon entropy of that distribution and the coefficient of variation. Use this when an agent already knows the product and needs to audit price fairness or detect outlier vendor pricing. Do NOT use as a discovery tool — it requires a known BuyWhere product_id from rank_buywhere_products_by_value_score. Requires a valid api_key (same as X-API-Key) and an x402 payment.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | API key required for this paid operation -- same secret configured as X-API-Key on the REST endpoints (BUYWHERE_API_KEYS). Payment (x402) alone is not sufficient; both gates must pass. | |
| product_id | Yes | BuyWhere internal product identifier as returned by rank_buywhere_products_by_value_score. Format: alphanumeric string. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but the description discloses the payment requirement (x402) and the need for an API key, and implies read-only behavior by stating it 'returns' data. Could additionally mention that it is a read operation with no side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences, front-loaded with purpose, followed by usage guidance and prerequisites. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description adequately explains the return value (price distribution, entropy, coefficient of variation) and mentions the payment and key requirements. Lacks details on potential failure modes or result format, but is sufficient for a tool with clear input from a sibling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema descriptions already fully cover both parameters (100% coverage). The description repeats some of that information but adds no significant new meaning beyond what is in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it returns a cross-vendor price distribution with entropy and coefficient of variation for a known product, distinguishing it from the sibling discovery tool rank_buywhere_products_by_value_score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use (audit price fairness, detect outliers) and when not to use (not a discovery tool), with clear prerequisite that product_id must come from the sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
nexus_useful_data_source_for_agents_doing_prod_rank_buywhere_products_by_value_scoreInspect
Searches the BuyWhere Singapore catalogue for products matching a natural-language query and returns them ranked by an auditable value-score derived from Shannon entropy of cross-vendor price variance, causal reliability, and price rank. Use this when an agent needs ranked product recommendations for a Singapore market query with auditable justification per product. Do NOT use for real-time stock ticker data, non-SGD markets, or exact product ID lookup (use fetch_buywhere_vendor_price_distribution for that). Requires a valid api_key (same as X-API-Key) and an x402 payment.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of ranked products to return. Higher values increase latency. Recommended 5-20 for agent consumption. | |
| query | Yes | Natural-language product description, e.g. 'noise-cancelling wireless headphones under SGD 300'. Must be in English. | |
| api_key | Yes | API key required for this paid operation -- same secret configured as X-API-Key on the REST endpoints (BUYWHERE_API_KEYS). Payment (x402) alone is not sufficient; both gates must pass. | |
| min_value_score | No | Minimum composite value-score [0.0, 1.0] a product must have to be included. Products below this threshold are excluded before ranking. |
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!
Your Connectors
Sign in to create a connector for this server.