Ayebot buyer index

Count acquirers by sector and market

count_buyers

Read-onlyIdempotent

Count how many acquirers on Ayebot's buyer register state an appetite for a sector in a Southeast Asian market. Use it for questions like "how many buyers are there for a healthcare business in Malaysia?" or "how many private equity buyers look at logistics in Singapore?". Give sector and market for one cell; sector only for that sector across all six markets; market only for every sector in that market; neither for register totals. Accepts keys (e.g. "fnb", "sg") or plain names (e.g. "food and beverage", "Singapore"). Returns aggregate counts split into strategic, private equity, family office and other. Never returns names. Call list_sectors_and_markets for valid values.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "count_buyers"
  }
}

Input Schema

Name	Required	Description	Default
`market`	No	Market key or name: sg, my, id, th, vn, ph (Singapore, Malaysia, Indonesia, Thailand, Vietnam, Philippines). Omit for all markets.
`sector`	No	Sector key or name, e.g. "healthcare", "F&B", "logistics". Omit for all sectors.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish this as a safe, idempotent, non-destructive read. The description adds real behavioral context beyond them: it explicitly states 'Never returns names' and that output is aggregate counts split into strategic, PE, family office and other, which sets correct expectations about the shape of the result.

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?

Front-loaded with the core action, then the when-to-use matrix, then format/sibling guidance. The two example questions consume space but usefully ground the tool's usage, so this is dense rather than padded.

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?

With no output schema and only two optional params, the description fully compensates: it explains the parameter matrix, accepted value formats, the split of returned counts, and the guarantee that no names are returned, plus a pointer to the tool that enumerates valid values.

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%, so the baseline is 3, but the description goes further by explaining the combinatorial semantics of sector+market and by noting that keys ('fnb', 'sg') or plain names ('food and beverage', 'Singapore') are both accepted, which the schema does not spell out as clearly.

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?

Specific verb (count) plus a precisely scoped resource (acquirers on Ayebot's buyer register expressing appetite for a sector in a Southeast Asian market). It is clearly distinguishable from siblings like buyer_appetite_summary and list_sectors_and_markets.

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

Usage Guidelines5/5

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

Explicitly enumerates the four parameter combinations and what each returns (one cell, one sector across six markets, one market across all sectors, register totals), gives concrete example questions, and routes the agent to list_sectors_and_markets for valid values.

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

All Ayebot buyer index tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?