Skip to main content
Glama

fundz

by net.fundz
OverviewDiscussionsAdmin

Search executive changes

search_executive_changes
Read-onlyIdempotent

Find executive appointments and departures. Search by role (CEO, CTO, CFO, etc.), change type (Appointment/Departure), company name, and date range. Set open_seats_only for officer seats that just opened at public companies: an 8-K departure where the filing names no permanent successor (exec search, recruiting and interim placements). Set source "sec_form3" for new officers taken from their own SEC Form 3 filing. Set source "job_posting" for C-level, president and general counsel seats that private companies are advertising on their own job boards (seats that never reach an SEC filing).

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.
sourceNoOnly hires from this source. "sec_form3" = new officers from their own SEC Form 3 filing (often roles below the C-suite that press releases miss). "job_posting" = open C-level / president / general counsel seats posted on private companies' own job boards (uses days up to 120, page and limit; other filters are ignored).
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"
role_typeNoExecutive role (e.g., "CEO", "CTO", "CFO", "CMO", "COO", "VP")
change_typeNoType of change: "Appointment" or "Departure"
company_nameNoFilter by company name
saved_filterNoName of one of the user's saved executive-changes filters (see get_saved_filters); its criteria are applied and any explicit filters above are added on top
executive_nameNoFilter by executive name
open_seats_onlyNoOnly officer seats that are still open: 8-K departures naming no permanent successor (none named, an interim in the seat, or a search announced) and no later hire filed. Public companies; uses company_name and days, other filters are ignored.
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. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Only hires from this source. \"sec_form3\" = new officers from their own SEC Form 3 filing (often roles below the C-suite that press releases miss)."New value: +"Only hires from this source. \"sec_form3\" = new officers from their own SEC Form 3 filing (often roles below the C-suite that press releases miss). \"job_posting\" = open C-level / president / general counsel seats posted on private companies' own job boards (uses days up to 120, page and limit; other filters are ignored)."
  3. Changed2 schema fields changed
    • addedInput schema / properties / open_seats_only
      Added value: +{
+  "description": "Only officer seats that are still open: 8-K departures naming no permanent successor (none named, an interim in the seat, or a search announced) and no later hire filed. Public companies; uses company_name and days, other filters are ignored.",
+  "type": "boolean"
+}
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Only hires from this source. \"sec_form3\" = new officers from their own SEC Form 3 filing (often roles below the C-suite that press releases miss).",
+  "type": "string"
+}
  4. 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 executive-changes 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"
+}
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningful behavioral context beyond that, notably that open_seats_only and job_posting silently ignore most other filters and that open seats means an 8-K departure with no permanent successor and no later hire filed.

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

Conciseness3/5

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

Front-loaded first sentence is good, but the second sentence restates the role/change_type/company_name/date-range parameters already fully documented in the schema, and the three 'Set X' sentences partially duplicate the parameter descriptions. Useful content, but a chunk does not earn its place.

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 15-parameter tool with mode-dependent filter interplay and no output schema, the description covers the special modes well but never states the default behavior when nothing is supplied (all parameters optional), nor how precedence works among days/since/saved_filter beyond what the schema says.

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; the description earns a step above by explaining the conceptual meaning of open_seats_only (no permanent successor, interim, search announced) and the two source values, which the schema only sketches. It does not add anything for the remaining eleven parameters.

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?

Opens with a specific verb+resource: "Find executive appointments and departures," then enumerates the filterable dimensions (role, change type, company, date range). This clearly separates it from siblings like search_layoffs or search_hiring_intel, though it never names an alternative explicitly.

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?

Gives concrete when-to-use guidance for each special mode: open_seats_only is tied to exec search, recruiting and interim placements; sec_form3 for officers below the C-suite that press releases miss; job_posting for private-company advertised seats. No explicit when-not-to-use or sibling routing, which keeps it from a 5.

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