Skip to main content
Glama

fundz

by net.fundz
OverviewDiscussionsAdmin

Search funding rounds

search_funding_rounds
Read-onlyIdempotent

Search funding rounds (the same feed as app.fundz.net/fundings). Filter by company name, industry, location (city/state/country), keywords, series, amount and date window, or run one of the user's saved filters by name. Page through every match with page, and get only new rounds with since. Filters are applied server-side, so the total_count is the filtered total.

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to look back (default 7)
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.
seriesNoFunding series (e.g., "Seed", "Series A", "Series B", "Series C")
industryNoIndustry title as used in Fundz, e.g. "Information Technology", "Financial Services", "Health Care"
keywordsNoFree-text keywords matched against the round's title and description, e.g. "fintech", "artificial intelligence"
locationNoCity, state/region or country title, e.g. "Colorado", "United States", "Denver", "United Kingdom"
company_nameNoCompany name (partial, case-insensitive), e.g. "Voxel"
saved_filterNoName of one of the user's saved filters (see get_saved_filters); its criteria are applied and any explicit filters above are added on top
max_money_raisedNoMaximum amount raised (in dollars)
min_money_raisedNoMinimum amount raised (in dollars, e.g., 1000000 for $1M)
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. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default 20, max 50)"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 / 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

A4.2/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive, open-world search. The description adds useful behavioral context beyond those annotations: filters are applied server-side and total_count reflects the filtered total, and it explains paging and since-based retrieval. It does not mention the per-account marker behavior of new_since_last_pull, but the schema covers that parameter directly.

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

Conciseness5/5

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

The description is three tight sentences: purpose first, filter/paging capabilities second, and server-side total_count behavior last. There is no redundant or wasted language.

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?

For a 13-parameter search tool with no output schema, the description covers purpose, main filter categories, saved filters, paging, since-based retrieval, and filtered total_count. The schema carries the detailed parameter semantics, so the remaining gap around full return-shape description is reasonable but keeps it from a 5.

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 parameter semantics are already fully documented in the input schema. The description groups the major filter categories and mentions saved filters, paging, and since, but it adds little semantic detail beyond what the schema already provides.

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?

The description states a specific verb and resource: 'Search funding rounds,' and anchors it to the Fundz funding-round feed. The resource is clearly distinct from sibling searches such as search_investors or search_acquisitions, so an agent can identify the correct tool without opening the 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?

The description gives clear usage context by enumerating the available filter dimensions and explaining saved-filter and paging behavior. It does not explicitly name when-not to use it or point to alternative sibling tools, so it falls short of full alternative routing guidance.

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