MentionFox

Companies with a filed reason to buy from you

find_buyers_now

Read-onlyIdempotent

Give the website of the business you sell for. MentionFox reads it to learn what you sell, then searches recent filed events for up to 10 companies with a reason to buy from you now: new funding filings, a new chief executive, finance chief, operations chief or general counsel, IPO filings, activist stakes of 5% or more, layoff filings and state layoff notices, crowdfunding raises and new Y Combinator companies. US companies only. Investment funds and real estate filings are left out. Every result carries the record it came from (record_url, for example the SEC filing or the state notice list), so you can check it yourself; the why_now line is written from that record, and fit is a short note on why the company matches what you sell. searched_feeds lists every feed searched with the date of its newest record. Fewer than 10 means fewer were found; the list is never padded. Costs 1 credit when companies come back; a search that finds none costs nothing. The same search is free to try at https://mentionfox.com/buyers. Plans and credits: https://mentionfox.com/pricing

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": {
      "url": "<url>"
    },
    "name": "find_buyers_now"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	The website of the business you sell for, for example acme.com.
`days`	No	How far back to look: 30 or 90 days.
`limit`	No	At most this many companies.
`state`	No	Optional. A two-letter US state code (for example TX) to keep only companies based there.
`trigger_types`	No	Optional. Only these kinds of event (layoff covers layoff filings and state layoff notices). Left out, the kinds that fit what you sell are chosen for you.

Output Schema

Name	Required	Description
`ok`	No	True when the search ran.
`days`	No	How many days back the search looked.
`count`	No	How many companies came back (never padded to 10).
`error`	No	Present when the call could not do the work; says why and that nothing was charged where that is so.
`offer`	No	What you sell, as read from that website.
`domain`	No	The website read to learn what you sell.
`status`	No	Why there is no list, when there is none.
`message`	No	A plain note about the answer, for example why candidates were returned instead of a result.
`results`	No	Each company: name, the event, why_now, fit and record_url, the record it came from.
`pricing_note`	No	What this call cost and what a repeat costs.
`searched_feeds`	No	Every feed searched, with the date of its newest record.
`credits_charged`	No	Credits this call took. 0 when nothing was charged.
`mentionfox_check`	No	Present when the call named a company MentionFox holds a record for: MentionFox's own check on it (the sentence, red flags and notes with their source links, how many sources) and a link to the full findings.
`see_it_on_the_web`	No	The same search on mentionfox.com.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedOutput schema / properties / mentionfox_check

Added value: +{
+  "description": "Present when the call named a company MentionFox holds a record for: MentionFox's own check on it (the sentence, red flags and notes with their source links, how many sources) and a link to the full findings."
+}

Changed1 schema field changedOct 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "How many companies came back (never padded to 10).",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "credits_charged": {
+      "description": "Credits this call took. 0 when nothing was charged.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "days": {
+      "description": "How many days back the search looked.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "domain": {
+      "description": "The website read to learn what you sell.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Present when the call could not do the work; says why and that nothing was charged where that is so.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "A plain note about the answer, for example why candidates were returned instead of a result.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "offer": {
+      "description": "What you sell, as read from that website.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ok": {
+      "description": "True when the search ran.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "pricing_note": {
+      "description": "What this call cost and what a repeat costs.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "description": "Each company: name, the event, why_now, fit and record_url, the record it came from.",
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "searched_feeds": {
+      "description": "Every feed searched, with the date of its newest record.",
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "see_it_on_the_web": {
+      "description": "The same search on mentionfox.com.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Why there is no list, when there is none.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "Companies with a filed reason to buy",
+  "type": "object"
+}

AddedOct 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare read-only, idempotent, open-world behavior; the description adds real substance on top: 1 credit charged only when results come back, zero cost on empty searches, results never padded, provenance via record_url, and searched_feeds exposing which feeds were queried and their freshness. That is exactly the kind of cost/coverage disclosure annotations cannot carry.

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 required action, then behavior, then cost — a sensible order with little filler. It loses a point for re-listing every trigger type already enumerated in the schema and for the trailing promotional links (free trial, pricing) that are not needed to invoke the tool correctly.

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?

For a 5-parameter, open-world search with an output schema, everything an agent needs is present: input meaning, geographic and category limits, default trigger selection, result-size honesty, cost model, and field-level meaning of the return. The output schema makes the return-value explanation optional, so its inclusion is surplus rather than a requirement.

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 adds meaning the schema does not: it explains that url is read to infer what you sell, that the cap is 10 companies, and crucially that omitting trigger_types makes the service pick event kinds matching your offering rather than defaulting to all. Only the days/state semantics are left entirely to the schema.

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 concrete action and resource: reads your website, then searches recent filed events for up to 10 companies with a buy signal, enumerating the event categories. It is clearly distinguishable from the person-centric siblings (enrich_person, compare_people, get_dossier) without opening any schema.

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?

Tells the agent the required input ('the website of the business you sell for'), scopes results to US companies, and explicitly excludes investment funds and real estate filings. It also points to a free web trial as an alternative route, though it never names a sibling tool or says when not to call this one.

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

All MentionFox 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?