Skip to main content
Glama

Find buyers

find_buyers
Read-onlyIdempotent

Who bought companies of a kind, in one call: the buyers named on every deal whose company matches, counted and ranked, the one on the most deals first. Say the kind of company by words its name holds (company, a list: every trade word the request names, searched together) and by sector (one or a list). Returns how many buyers and deals match, and each buyer with its firm record where it is a firm in the database, how many matching deals it did, its latest, and the companies it bought. With include_contacts, each firm's own mailboxes and phone lines are in its row, using one credit from the account's monthly allowance for each firm opened. Use this, never one search_deals a word, whenever the question is who buys, acquires or invests in companies like these.

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": "find_buyers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results, from 1.
limitNoHow many buyers to return, 1 to 50.
sectorNoThe bought company's sector, or a list of sectors searched together: AI & Data, Aerospace & Defense, Agriculture, Business Services, Construction & Infrastructure, Consumer & Retail, Education, Energy & Power, Financial Services, Food & Beverage, Government & Nonprofit, Healthcare Services, Hospitality & Leisure, Industrials & Manufacturing, Insurance, Life Sciences & Pharma, Media & Entertainment, Medical Devices, Real Estate, Software & IT, Telecom, Transportation & Logistics, Other. With company, a deal must match both.
companyNoWords a bought company's name holds, as a list of up to 20 searched together in this one call: ["utility", "substation", "excavat", "directional"]. A deal matches when its company's name holds any of them, so give every trade word the request names, each in the shortest form that covers its endings ("excavat" finds Excavating and Excavation). Deals carry no NAICS code: words in the name and the sector are how a kind of company is found.
year_toNoLast year, inclusive.
deal_typeNoOnly deals of this kind.
year_fromNoFirst year, inclusive.
max_value_musdNoHighest disclosed value, in millions of US dollars.
min_value_musdNoLowest disclosed value, in millions of US dollars. Only deals with a disclosed value match.
include_contactsNoAlso return each buyer's own mailboxes and phone lines in its row, where the buyer is a firm in the database. Each firm whose contact is opened uses one credit from the account's monthly allowance, the same credits a person's contact uses; a firm with none on file costs nothing, and one already opened this month is free. Use it only when the person asks for contact details, and say how many credits it used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the ranking order, the exact contents of each result row, and the credit accounting rule (one credit per firm opened, free if already opened this month or if no contact is on file). That credit disclosure is the most valuable part and is not derivable from any structured field.

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

Conciseness3/5

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

There is no filler, but the structure is poor: a single 40-word opening sentence built from stacked clauses, followed by another long sentence that interleaves returns, credits and alternatives. The most decision-relevant instruction ('use this, never search_deals') is buried at the very end rather than front-loaded.

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?

With 10 optional parameters and no output schema, the description carries the return-value burden and does so: it states what counts are returned, what each buyer row contains, and how ranking works. Pagination is left entirely to the schema, which documents it, so the remaining gap is minor.

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. The description goes beyond it by explaining the strategy for the company parameter: pass every trade word the request names, each in the shortest form that covers its endings ('excavat' finds Excavating and Excavation), and combine words with sector as an AND. That is operational guidance the schema text only partially implies.

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 names a specific resource (buyers on deals whose company matches) and an output shape (counted, ranked, most deals first), and explicitly separates itself from search_deals. However, the opening clause is a tangled appositive chain ('the buyers named on every deal whose company matches, counted and ranked, the one on the most deals first') that forces the agent to reconstruct the verb rather than read it plainly.

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?

It gives a clear routing rule with a named alternative: use this 'never one search_deals a word, whenever the question is who buys, acquires or invests in companies like these.' It also constrains include_contacts to 'only when the person asks for contact details.' What it lacks is any when-not condition for this tool itself (e.g. when deal-level detail is wanted instead of ranked buyers).

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.

Resources