Skip to main content
Glama

Vibe Springs

by net.vibesprings

get_listing_intel

Audit your own x402 listings against the live Bazaar catalogue. Authenticity scoring separates genuine demand from self-traffic (the catalogue's highest-volume listings are frequently a merchant calling itself), listing-health diagnostics explain why a listing takes no paid calls, and price-band guidance is drawn from what measurably sells. Includes your revenue percentile across all indexed merchants. [PAID: $1 USDC per call via x402 on Base. First call without payment_signature returns the payment requirements.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOptional keyword to scope pricing guidance to comparable services.
domainNoMerchant domain to audit, e.g. example.com. Provide this or pay_to.
pay_toNoReceiving wallet address (0x...) whose listings should be audited.
payment_signatureNoOptional x402 payment token. Call the tool WITHOUT this first to receive payment requirements (price, payTo, asset, nonce rules), sign the exact-scheme EIP-712 USDC authorization with your wallet, then retry with this field set to the base64 token.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description fully discloses the paid nature ($1 USDC per call via x402), the two-step payment process (first call returns requirements, second with signature), and the scope (own listings only). This is comprehensive behavioral information beyond what annotations could provide.

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 well-structured with a clear topical lead sentence followed by specific capabilities and a payment note. Every sentence adds unique value without redundancy, and the payment details are logically placed at the end.

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?

The description adequately covers what the tool does, its payment model, and the three key outputs. However, it lacks details on the output format (e.g., JSON structure, error handling), which would be beneficial given the absence of an output schema. The tool is complex enough that a minimal output hint would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing descriptions for all four parameters. The tool description adds extra context for payment_signature by explaining the x402 workflow, and clarifies the purpose of tag for scoping pricing guidance. This adds value beyond the schema, especially for the payment flow.

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 starts with a clear verb 'Audit' and specific resource 'your own x402 listings', listing three concrete outputs (authenticity scoring, listing-health diagnostics, price-band guidance). This distinguishes it from sibling tools like check_listing_health or get_bazaar_competitors, which focus on different aspects.

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 implicitly states it's for auditing one's own listings ('Audit your own x402 listings'), which guides the agent to use it for self-audit rather than general marketplace analysis. However, it does not explicitly compare with siblings or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vibe Springs toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but get_crypto_prices overlaps partially with get_market_pulse (which includes crypto prices), and get_exchange_rates overlaps with convert_currency. Descriptions clarify boundaries, but minor confusion possible.

Naming Consistency4/5

Nearly all tools follow a get_<noun> or verb_noun pattern, with consistent snake_case. The only outlier is 'health' which is a single word, but it still fits as a status endpoint.

Tool Count4/5

22 tools is slightly high for a single server, but each tool offers a distinct paid endpoint and the variety justifies the count. The server would benefit from a bit more focus, but it's still acceptable.

Completeness4/5

The server covers a wide range of data (crypto, weather, finance, on-chain risk, travel) with search and health endpoints. Missing operations like delete_watch or list_watches are minor gaps, but core functionality is well represented.

Resources