Skip to main content
Glama

match_verified_buyers_by_intent

[Opt-in buyers only] Seller: find buyers who have budget for what you sell in your category; your first 3 matches have no extra fee. Example: sellerStoreId='quantalpha-institutional-node'.

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
sellerStoreIdYesRegistered seller store ID holding a 2★ or 3★ VERITAS-8183 Seal.
dealAmountUsdcNoProposed order amount in USDC when closing a matched deal.
targetVerticalNoVertical category to match buyer intent.
directOfferPitchNoShort offer message sent to the matched buyer.
minAvailableBudgetUsdcNoMinimum verified remaining daily USDC budget required.
minPaymentReliabilityPctNoMinimum historical payment completion percentage (0 to 100).
connectAndCloseDealWithBuyerIdNoOptional buyer ID to send a direct pitch and close a matched order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / connectAndCloseDealWithBuyerId / description
      Previous value: -"Optional Buyer ID to send a direct verified offer and close a matched deal."New value: +"Optional buyer ID to send a direct pitch and close a matched order."
    • addedInput schema / properties / dealAmountUsdc / description
      Added value: +"Proposed order amount in USDC when closing a matched deal."
    • addedInput schema / properties / directOfferPitch / description
      Added value: +"Short offer message sent to the matched buyer."
    • changedInput schema / properties / minAvailableBudgetUsdc / description
      Previous value: -"Filter buyers by minimum verified daily USDC budget available right now."New value: +"Minimum verified remaining daily USDC budget required."
    • addedInput schema / properties / minPaymentReliabilityPct / description
      Added value: +"Minimum historical payment completion percentage (0 to 100)."
    • changedInput schema / properties / sellerStoreId / description
      Previous value: -"Your registered seller Store ID (must hold 2-Star or 3-Star VERITAS-8183 Seal)."New value: +"Registered seller store ID holding a 2★ or 3★ VERITAS-8183 Seal."
    • addedInput schema / properties / sellerStoreId / examples
      Added value: +[
      +  "quantalpha-institutional-node"
      +]
    • addedInput schema / properties / targetVertical / description
      Added value: +"Vertical category to match buyer intent."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false with the schema exposing directOfferPitch and connectAndCloseDealWithBuyerId, so the 'find buyers' framing understates that this tool can message buyers and close deals. The description does add useful non-annotation behavior: the opt-in-only buyer pool and the free-trial quota of three matches. That covering of cost and eligibility is real value, but the undisclosed side effects keep it at a 3.

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

Conciseness4/5

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

A single front-loaded sentence with the eligibility constraint bracketed at the front and the fee note attached to matching. The trailing example restates what the schema's examples field already provides, making it the one lightly redundant element.

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?

There is no output schema, but for a seven-parameter match tool with fully documented parameters, the description supplies the missing essentials: audience, eligibility restriction, and cost model. The omission of return shape is minor given that the schema carries all argument semantics.

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 description coverage is 100%, so the baseline is 3. The description echoes the sellerStoreId example and implies category and budget filtering, but adds no syntax or semantics beyond what the schema already documents for dealAmountUsdc, minPaymentReliabilityPct, or the vertical enum.

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

Purpose4/5

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

The description states a specific verb and resource ('find buyers who have budget for what you sell in your category'), which is concrete enough to distinguish matching from a generic store listing. It does not, however, distinguish itself from siblings like discover_verified_stores, which an agent would likely consider alongside it.

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?

It names the intended caller ('Seller:') and a constraint ('Opt-in buyers only'), and adds commercial context about the first 3 matches being free. It gives no explicit when-not-to-use guidance or comparison to alternative discovery tools, leaving the choice to inference.

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.