Buyer Signals

Find companies with buyer signals

find_buyer_signals

Read-onlyIdempotent

Use this when the user wants companies that recently raised money or have long-open roles, such as "which software companies in Texas filed a Form D this month?" or "find companies with a bookkeeper role open 60+ days". Pass the industry, and optionally the region, the role the user's service replaces, lookback_days (1 to 60, default 14) and limit. Returns companies ranked by score, each with a one-line why and dated signals linking to the SEC filing or job posting. Roles are only checked when a role is given, and only on the public boards of the companies found. A Form D shows funding, not intent to buy. Companies only: no people or contact details.

Input Schema

TableJSON Schema

Name	Required	Description
`role`	No	The job your service replaces or supports, such as "bookkeeper" or "customer support". When given, public job boards of the companies found are checked for matching roles open 60 or more days
`limit`	No	How many companies to return (default 10)
`region`	No	Where the company is based: any US state (name or two-letter code), "US", United Kingdom, Canada, Israel, Ireland, Singapore, Australia, Hong Kong. Leave out to search everywhere
`industry`	Yes	The buyer's industry: software_it (software, SaaS, IT, AI), telecom, biotech_pharma, healthcare, business_services (agencies, consultancies, staffing), manufacturing, retail_consumer, construction, real_estate, energy, environmental, agriculture, mining or travel_hospitality
`lookback_days`	No	How many days back to look for filings (default 14)

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	Yes
`leads`	Yes
`notice`	Yes
`region`	Yes
`status`	Yes
`window`	Yes
`message`	No
`sources`	Yes
`industry`	Yes
`open_roles`	Yes
`filings_found`	Yes
`companies_checked`	Yes
`note_from_openkrill`	No	Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's job is added context, and it delivers: roles are only checked when a role is supplied and only on public boards of found companies, and it warns that "A Form D shows funding, not intent to buy." It also scopes the result to companies only (no people/contacts). It stops short of discussing rate limits or coverage caveats.

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 trigger condition and examples, then the parameters, then the return shape and caveats. Dense but each sentence carries information; the enumeration of parameters is slightly redundant with the schema but not wasteful.

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?

Covers trigger, inputs, ranking/return shape (score, one-line why, dated signal links) and key limitations, and an output schema exists so return values need not be fully spelled out. A minor gap is that it never states whether results are capped by lookback/limit interaction or how to broaden a too-narrow search.

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 restates the same parameter semantics (lookback_days 1-60 default 14, role meaning, industry/region) already documented in the schema, adding no format or edge-case detail beyond it.

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?

States a specific verb (find) and resource (companies with buyer signals) and pins it down with concrete example queries (Form D filings, 60+ day open roles). An agent can distinguish this from the sibling tools, none of which relate to company signal search.

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?

"Use this when the user wants companies that recently raised money or have long-open roles" gives a clear trigger, reinforced by two natural-language example queries. It does not name an alternative tool or an explicit when-not-to-use case, which keeps it short of a 5.

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

All Buyer Signals 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?