Skip to main content
Glama

fundz

by net.fundz
OverviewDiscussionsAdmin

Search major events

search_major_events
Read-onlyIdempotent

Material corporate events drawn from SEC filings, each with a plain-English description and a category (executive change, acquisition, funding, contract, product launch, expansion, regulatory and so on). Broader than search_sec_filings: use this to scan for what materially happened, and search_sec_filings when the user wants the filings themselves.

Input Schema

NameRequiredDescriptionDefault
daysNoDays 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.
categoryNoEvent category. hiring = executive changes, acquisition = M&A, funding = financial events.
company_nameNoCompany name (partial, case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Event category to filter on, e.g. \"leadership\", \"M&A\""New value: +"Event category. hiring = executive changes, acquisition = M&A, funding = financial events."
    • addedInput schema / properties / category / enum
      Added value: +[
+  "funding",
+  "hiring",
+  "acquisition",
+  "contract_agreement",
+  "product_launch",
+  "award",
+  "company_expansion",
+  "regulatory_change",
+  "rapid_growth",
+  "other"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum 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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description's added value is provenance and result shape — SEC filing sourcing and the plain-English description/category per event. It does not address data freshness, quota cost, or result volume caps, so it stops short of full behavioral disclosure.

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?

Two sentences, front-loaded with what the tool returns before the routing guidance. Every clause earns its place; nothing is repeated from the schema.

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?

There is no output schema, and the description compensates by describing the fields of each returned event. Combined with the thorough parameter descriptions, an agent has enough to call it correctly; only secondary details like result volume or freshness are absent.

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 defaults, ranges, pagination, and the enum are fully documented in the schema itself. The description's category list (executive change, acquisition, funding, contract, product launch, expansion, regulatory) loosely echoes the enum without adding syntax or usage detail beyond it, so baseline 3 applies.

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 resource (material corporate events from SEC filings), what each result contains (plain-English description plus a category), and explicitly contrasts its breadth against search_sec_filings. An agent can distinguish it from the filing-level sibling without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing: use this to scan for what materially happened, use search_sec_filings when the user wants the filings themselves. The when-to-use and the alternative are both named outright, leaving no inference required.

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