Skip to main content
Glama

fundz

by net.fundz
OverviewDiscussionsAdmin

Search acquisitions

search_acquisitions
Read-onlyIdempotent

Search for acquisition events. Filter by deal value, acquirer name, target company, deal type, and date range.

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to look back (e.g., 7, 30, 60)
pageNoPage number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more.
limitNoResults per page (default 20, max 50)
sinceNoOnly results Fundz added on or after this ISO date, e.g. "2026-10-01" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new.
industryNoIndustry title, e.g. "Information Technology"
keywordsNoFree-text keywords matched against title/description (comma-separated for several)
locationNoCity, state or country title, e.g. "Texas"
target_nameNoFilter by target company name
company_nameNoCompany name (partial match)
saved_filterNoName of one of the user's saved acquisitions filters (see get_saved_filters); its criteria are applied and any explicit filters above are added on top
acquirer_nameNoFilter by acquiring company name
max_deal_valueNoMaximum deal value (in dollars)
min_deal_valueNoMinimum deal value (in dollars, e.g., 50000000 for $50M)
new_since_last_pullNoOnly rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / new_since_last_pull
      Added value: +{
+  "description": "Only rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account.",
+  "type": "boolean"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default: 20)"New value: +"Results per page (default 20, max 50)"
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more.",
+  "type": "number"
+}
    • addedInput schema / properties / saved_filter
      Added value: +{
+  "description": "Name of one of the user's saved acquisitions filters (see get_saved_filters); its criteria are applied and any explicit filters above are added on top",
+  "type": "string"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new.",
+  "type": "string"
+}
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing behavioral beyond that: it does not mention pagination, the per-account marker behavior of new_since_last_pull, or that it requires a signed-in account — all of which live only in the parameter schema.

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?

Two short sentences with the purpose front-loaded and no filler. The filter enumeration is partly redundant with the schema and includes one inaccurate item, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter, mutation-free search tool with rich schema descriptions and annotations, the description is adequate but thin. It leaves the incremental-sync path and sibling disambiguation entirely to the schema and the agent's inference.

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 coverage is 100%, so the schema already documents all 14 parameters and the baseline is 3. The description's filter list covers only a subset and omits the most distinctive parameters (new_since_last_pull, saved_filter, since), and it names 'deal type' which is not an actual parameter, which risks an agent inventing that argument.

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?

States a specific verb and resource: 'Search for acquisition events.' An agent can tell this apart from search_agreements or search_funding_rounds at a glance. It does not explicitly name those siblings or state how acquisitions differ from them, so it stops short of 5.

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

Usage Guidelines2/5

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

The second sentence lists filters, which is schema restatement, not usage guidance. There is no statement of when to prefer this tool over the roughly twenty sibling search tools, no mention of get_saved_filters for saved criteria, and no mention of when to use new_since_last_pull versus days/since for incremental pulls.

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

All fundz toolsInspect
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