Skip to main content
Glama

fundz

by net.fundz
OverviewDiscussionsAdmin

Search crowdfunding rounds

search_crowdfunding
Read-onlyIdempotent

Find crowdfunding campaigns. Search by offering amount, deadline, offered types (Common Stock, etc.), and portal.

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"
company_nameNoCompany name (partial match)
offered_typesNoType of security offered (e.g., "Common Stock")
max_offering_amountNoMaximum offering amount (in dollars)
min_offering_amountNoMinimum offering amount (in dollars)
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)"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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no pagination behavior, no note that `new_since_last_pull` maintains per-account state, and it references unsupported facets ('deadline', 'portal'), which adds noise rather than context.

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, front-loaded with the purpose and free of padding. The only flaw is that the second sentence spends words on filters that aren't in the schema.

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?

With 12 optional parameters and no output schema, the description should at minimum signal that results are paginated and that a stateful 'new only' mode exists; the schema covers this, so the gap is survivable. But the misleading 'deadline'/'portal' references and absence of any alternative routing leave it only minimally adequate.

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 schema already explains every parameter in detail; baseline 3 applies. The description merely echoes offering amount and offered types while introducing 'deadline' and 'portal', which are not actual parameters and could mislead an agent into searching for filters that do not exist.

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 ('Find crowdfunding campaigns') and enumerates the searchable facets, so an agent can tell it retrieves campaign listings. However it never distinguishes itself from the close sibling `search_funding_rounds`, and it names a 'deadline' filter that does not exist in 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 Guidelines2/5

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

There is no guidance on when to reach for this tool over `search_funding_rounds`, `search_investors`, or `get_daily_leads`, and no mention of prerequisites such as the signed-in account required by `new_since_last_pull`. Usage must be inferred entirely from the name.

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