Skip to main content
Glama

match_verified_buyers_by_intent

[EN] VERITAS-8183 Exclusive Buyer Intent & Solvency Matchmaker (2-Star & 3-Star Sellers Only). Lets certified sellers discover which AI buyers are actively looking to buy their vertical right now, filtered by verified available USDC budget and payment reliability. 3-Star (⭐⭐⭐) sellers unlock exclusive First-Look access to VIP Gold Institutional Buyers. Freemium model: first 3 matched clients (or 30 days) at 0.0% extra fee, then +0.5% success fee per matched client. | [ES] Radar exclusivo de compradores calificados (solo para vendedores 2★ y 3★): filtra clientes por capital disponible y qué buscan comprar. Vendedores 3★ tienen acceso prioritario directo a los mejores clientes. Freemium: primeros 3 clientes sin recargo extra, luego +0.5% por cliente conectado. | [中文] VERITAS-8183 认证买家意向与资金匹配雷达(仅限 2 星与 3 星卖家,3 星卖家独享 VIP 机构大买家优先直连;前 3 名成交客户免费,之后每单仅加收 0.5% 撮合费)。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sellerStoreId": "<sellerStoreId>"
    },
    "name": "match_verified_buyers_by_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerStoreIdYesYour registered seller Store ID (must hold 2-Star or 3-Star VERITAS-8183 Seal).
dealAmountUsdcNo
targetVerticalNo
directOfferPitchNo
minAvailableBudgetUsdcNoFilter buyers by minimum verified daily USDC budget available right now.
minPaymentReliabilityPctNo
connectAndCloseDealWithBuyerIdNoOptional Buyer ID to send a direct verified offer and close a matched deal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose something valuable the schema doesn't: tier gating and a real fee schedule (0.0% for the first 3 matches/30 days, then +0.5% per match). It omits the significantly more important behavior that the optional connectAndCloseDealWithBuyerId parameter transmits a binding offer and closes a deal, and it says nothing about what a non-eligible seller sees when rejected or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The same content is repeated verbatim in English, Spanish, and Chinese, roughly tripling length for a single-audience model, and marketing copy plus emoji stars consume space ahead of operational details. The genuinely useful scope sentence is present but not front-loaded in a scannable way.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 7-parameter tool with an embedded irreversible mutation (sending a verified offer and closing a deal), a fee model, and tier-based access control, and it has no annotations and no output schema. The description should explain return shape and the consequences of the deal-closing parameter; it covers none of that, leaving the promotional text to stand in for operational detail.

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

Parameters2/5

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

Schema coverage is only 43% across 7 parameters, so the description needed to compensate. It only gestures at the budget/reliability/vertical filters in prose; dealAmountUsdc, directOfferPitch, minPaymentReliabilityPct, and the entire offer-and-close flow go unexplained, and the relationship between dealAmountUsdc and the match results is left to guesswork.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The English sentence "Lets certified sellers discover which AI buyers are actively looking to buy their vertical right now, filtered by verified available USDC budget and payment reliability" is a specific verb plus resource. However, it is buried under a product code (VERITAS-8183), emoji star tiers, and pricing boilerplate, and the description never mentions that the tool can also send an offer and close a deal, which is half of what the schema allows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Eligibility is stated explicitly (2-Star/3-Star VERITAS-8183 Seal holders only, with 3-Star first-look access), which is useful context. But there is no when-to-use vs. when-not guidance, no mention of the sibling discovery/audit tools, and no advice on when to pass connectAndCloseDealWithBuyerId versus doing a lookup only.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.