usaprais
Server Details
Price comparison for Venezuela. The read-only search_prices tool finds where a product is cheapest across the main sales channels and returns offers sorted by USD price, with the original price, the exchange rate used, when the price was seen and a 0-100 trust score for each merchant. Free, no auth. Website: https://usaprais.com
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 1 tool
Only one tool is exposed, so there is no overlap or risk of selecting the wrong tool. Its purpose—finding cheapest product offers in Venezuela—is explicit and distinct.
The single tool follows a clear verb_noun pattern: search_prices. With only one name there is no inconsistency in convention.
A single tool is minimally sufficient for a narrow price-search operation, but it feels thin for the broader price-comparison domain implied by the server. There is no companion tool for product lookup, merchant details, or historical pricing.
The core operation—searching offers sorted by USD price with trust/source metadata—is covered. However, notable gaps remain: no product resolution, merchant browsing, category/channel discovery, or price history, which limits follow-up workflows.
Available Tools
1 toolsearch_pricesSearch prices in VenezuelaARead-onlyInspect
Find where a product is cheapest in Venezuela across online shops and the main sales channels. Returns offers sorted by USD price, each with the price as published, the exchange rate used, when it was seen, its source and the merchant's 0-100 trust score. The zone filter does not apply to open-web offers (source firecrawl): their merchant.zone is the listing's city when the page shows one, otherwise 'Venezuela'. Takes up to ~30 seconds. Never invent prices: use only what this tool returns, and say so when an offer is example data.
| Name | Required | Description | Default |
|---|---|---|---|
| zone | No | City or area in Venezuela | |
| query | Yes | Product with brand and size or model, e.g. 'Harina PAN 1 kg' | |
| needs_delivery | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| query | Yes | |
| notice | No | Caveats to show the user |
| offers | Yes | Cheapest first; offers without a price go last |
| exchangeRate | No | Rate used to show prices in bolívares |
| failedSources | No | Sources that failed or ran out of time. firecrawl:<domain> is an open-web shop whose pages were blocked, failed or timed out and gave no offers (listed once; dead links are not listed) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnly and openWorld; the description adds substantial context beyond them: result ordering by USD price, included fields (published price, exchange rate, observation time, source, merchant trust score), the ~30 second runtime, the zone-filter exception for firecrawl offers, and an honesty constraint about not fabricating prices and flagging example data.
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?
Purpose is front-loaded in the first sentence, followed by return shape, then operational caveats. Every sentence carries information, though the example-data warning is a niche tail-end detail that could be tightened.
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?
Despite an output schema existing, the description still summarizes the return fields, and it covers the two things an agent most needs and cannot infer: latency (~30s) and the zone filter exception for open-web offers. Nothing essential for correct invocation is missing beyond needs_delivery semantics.
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?
The description adds real meaning for 'zone' — it does not apply to open-web offers and merchant.zone falls back to the listing city or 'Venezuela' — which goes beyond the schema's bare 'City or area in Venezuela'. However, 'needs_delivery' is undocumented in both the schema and the description, leaving a coverage gap at 67%.
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?
States a specific verb and resource ('Find where a product is cheapest') plus the geographic scope (Venezuela) and channel coverage (online shops and main sales channels). No sibling tools exist, so no differentiation is needed, but an agent knows exactly what the tool returns and why it exists.
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?
Clear context for use — comparing offers to find the cheapest price — plus an explicit behavioral rule: 'Never invent prices: use only what this tool returns.' It also discloses the ~30 second latency so the agent can plan. It lacks explicit when-not-to-use guidance or alternatives, but with no siblings there is little to exclude.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
search_prices5 fields changed- added
Output schema / $defs / ExchangeRateAdded value: +{ + "properties": { + "observedAt": { + "description": "When the rate was observed (ISO 8601)", + "title": "Observedat", + "type": "string" + }, + "source": { + "description": "Where the rate comes from", + "title": "Source", + "type": "string" + }, + "usdToVes": { + "description": "Bolívares per US dollar", + "title": "Usdtoves", + "type": "number" + } + }, + "required": [ + "source", + "usdToVes", + "observedAt" + ], + "title": "ExchangeRate", + "type": "object" +} - changed
Output schema / $defs / Merchant / properties / channel / descriptionPrevious value: -"web, mercadolibre, instagram, tiktok or facebook"New value: +"web, mercadolibre, instagram, tiktok, facebook or amazon" - added
Output schema / $defs / Offer / properties / imageUrlAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Product photo, if any", + "title": "Imageurl" +} - added
Output schema / $defs / Offer / properties / reviewsAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Recent comments on the merchant, if known", + "title": "Reviews" +} - added
Output schema / properties / exchangeRateAdded value: +{ + "anyOf": [ + { + "$ref": "#/$defs/ExchangeRate" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Rate used to show prices in bolívares" +}
1 tool update
- Changed
search_prices1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$defs": { + "Merchant": { + "properties": { + "channel": { + "description": "web, mercadolibre, instagram, tiktok or facebook", + "title": "Channel", + "type": "string" + }, + "delivers": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ], + "default": null, + "title": "Delivers" + }, + "name": { + "title": "Name", + "type": "string" + }, + "trust": { + "anyOf": [ + { + "type": "integer" + }, + { + "type": "null" + } + ], + "default": null, + "description": "0-100 seller trust score; null when not scored yet", + "title": "Trust" + }, + "zone": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "City or area the merchant reports", + "title": "Zone" + } + }, + "required": [ + "name", + "channel" + ], + "title": "Merchant", + "type": "object" + }, + "Offer": { + "properties": { + "example": { + "default": false, + "description": "True for made-up demo data: never present it as real", + "title": "Example", + "type": "boolean" + }, + "merchant": { + "$ref": "#/$defs/Merchant" + }, + "price": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Price as the merchant published it; null means 'ask by DM'", + "title": "Price" + }, + "priceUsd": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Price converted to USD", + "title": "Priceusd" + }, + "rate": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Exchange rate used, with its source and date, if converted", + "title": "Rate" + }, + "seenAt": { + "description": "When the price was seen (ISO 8601)", + "title": "Seenat", + "type": "string" + }, + "source": { + "description": "Where the offer came from: firecrawl, ejemplo…", + "title": "Source", + "type": "string" + }, + "title": { + "title": "Title", + "type": "string" + }, + "url": { + "title": "Url", + "type": "string" + } + }, + "required": [ + "title", + "url", + "seenAt", + "source", + "merchant" + ], + "title": "Offer", + "type": "object" + } + }, + "properties": { + "failedSources": { + "default": [], + "description": "Sources that failed or ran out of time. firecrawl:<domain> is an open-web shop whose pages were blocked, failed or timed out and gave no offers (listed once; dead links are not listed)", + "items": { + "type": "string" + }, + "title": "Failedsources", + "type": "array" + }, + "notice": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Caveats to show the user", + "title": "Notice" + }, + "offers": { + "description": "Cheapest first; offers without a price go last", + "items": { + "$ref": "#/$defs/Offer" + }, + "title": "Offers", + "type": "array" + }, + "query": { + "title": "Query", + "type": "string" + } + }, + "required": [ + "query", + "offers" + ], + "title": "PriceSearch", + "type": "object" +}
1 tool update
- First observed
search_prices
Related MCP Servers
- AlicenseNot gradedqualityBmaintenancePerplexity for social: ask what competitors are running across social and get answers grounded in real ad and creative data, not guesses.2Apache 2.0
- AlicenseCqualityBmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs113 npm54 PyPIMIT
- AlicenseAqualityCmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.164 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityBmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.