Skip to main content
Glama
Fund-z

FundzWatch MCP Server

get_events

Retrieve real-time business events including funding rounds, acquisitions, and executive hires. Filter by type, industry, and location to track market developments.

Instructions

Get real-time business events: funding rounds, acquisitions, executive hires, government contracts, and product launches. Filter by type, industry, and location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typesNoComma-separated: funding, acquisition, hiring, contract, product_launch. Default: all
daysNoLook back days (1-90). Default: 7
limitNoMax events (1-200). Default: 50
industriesNoComma-separated industries
locationsNoComma-separated locations

Implementation Reference

  • The 'get_events' tool handler, which calls the '/events' API endpoint with parameters such as types, days, limit, industries, and locations.
    case "get_events": {
      const data = await apiRequest("GET", "/events", {
        types: (args as any).types,
        days: (args as any).days,
        limit: (args as any).limit,
        industries: (args as any).industries,
        locations: (args as any).locations,
      });
      const events = data.events || [];
      if (events.length === 0) {
        return textResult("No events found matching your filters.");
      }
      const summary = events
        .map((e: any, i: number) => {
          let detail = `${i + 1}. [${e.type.toUpperCase()}] ${e.title}`;
          if (e.amount) detail += ` ($${(e.amount / 1_000_000).toFixed(1)}M)`;
          if (e.series) detail += ` - ${e.series}`;
          if (e.date) detail += ` | ${e.date}`;
          return detail;
        })
        .join("\n");
      return textResult(`${data.total} events found (showing ${events.length}):\n\n${summary}`);
    }
    
    case "get_market_pulse": {
      const data = await apiRequest("GET", "/market/pulse");
      const p = data.pulse;
  • The input schema definition for 'get_events', documenting the available parameters like types, days, limit, industries, and locations.
    {
      name: "get_events",
      description:
        "Get real-time business events: funding rounds, acquisitions, executive hires, " +
        "government contracts, and product launches. Filter by type, industry, and location.",
      inputSchema: {
        type: "object" as const,
        properties: {
          types: { type: "string", description: "Comma-separated: funding, acquisition, hiring, contract, product_launch. Default: all" },
          days: { type: "number", description: "Look back days (1-90). Default: 7" },
          limit: { type: "number", description: "Max events (1-200). Default: 50" },
          industries: { type: "string", description: "Comma-separated industries" },
          locations: { type: "string", description: "Comma-separated locations" },
        },
      },
    },
Behavior3/5

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

Adds 'real-time' context not in schema, which is valuable. However, with no annotations provided, the description should disclose more: authentication requirements, rate limits, pagination behavior, or failure modes when no events match filters.

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 well-structured sentences with the specific examples front-loaded. Suffers only slightly from not mentioning the temporal window (days parameter) which is a key behavioral constraint.

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?

Adequate for 5 parameters with complete schema coverage and no output schema, but lacks temporal scope clarification (the lookback window is only in schema) and differentiation from similar event-retrieval siblings.

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%, establishing baseline 3. Description mentions filtering by 'type, industry, and location' which maps to parameters, but adds no syntax clarification beyond the schema's comma-separated format notes.

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?

Clearly states the tool retrieves business events (funding, acquisitions, etc.) with specific resource types listed. However, it fails to distinguish from sibling tool get_watchlist_events, which also presumably retrieves events.

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?

Provides no guidance on when to use this general event feed versus alternatives like get_watchlist_events (user-curated) or get_market_brief. No prerequisites or exclusion criteria mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fund-z/fundzwatch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server