Skip to main content
Glama
Fund-z

FundzWatch MCP Server

get_watchlist_events

Retrieve recent business events for companies on your watchlist, including funding rounds, acquisitions, executive hires, and contracts, to monitor market activity.

Instructions

Get recent events for companies on your watchlist: funding, acquisitions, executive hires, contracts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLook back days (1-90). Default: 7
typesNoComma-separated event types

Implementation Reference

  • The handler implementation for the get_watchlist_events tool, which fetches event data from the API based on user-provided parameters.
    case "get_watchlist_events": {
      const data = await apiRequest("GET", "/watchlist/events", {
        days: (args as any).days,
        types: (args as any).types,
      });
      const events = data.events || [];
      if (events.length === 0) {
        return textResult(
          `No events found for your ${data.tracked_companies} tracked companies in the last ${data.period_days} days.`
        );
      }
      const summary = events
        .map((e: any, i: number) => {
          let detail = `${i + 1}. [${e.type.toUpperCase()}] ${e.company_name}: ${e.title}`;
          if (e.amount) detail += ` ($${(e.amount / 1_000_000).toFixed(1)}M)`;
          if (e.date) detail += ` | ${e.date}`;
          return detail;
        })
        .join("\n");
      return textResult(`${data.total} events for ${data.tracked_companies} tracked companies:\n\n${summary}`);
    }
  • The schema definition and registration for the get_watchlist_events tool.
      name: "get_watchlist_events",
      description:
        "Get recent events for companies on your watchlist: funding, acquisitions, " +
        "executive hires, contracts.",
      inputSchema: {
        type: "object" as const,
        properties: {
          days: { type: "number", description: "Look back days (1-90). Default: 7" },
          types: { type: "string", description: "Comma-separated event types" },
        },
      },
    },
Behavior3/5

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

No annotations provided, so description carries full burden. 'Recent' alludes to temporal filtering (aligns with 'days' parameter) and enumerated event types hint at valid values for 'types' parameter. However, lacks disclosure on pagination, empty result handling, rate limits, or data freshness.

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?

Single sentence, front-loaded with action verb. Colon-separated list efficiently documents event categories without verbosity. No redundant or wasted text.

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 a 2-parameter tool with complete schema coverage. Description explains what is retrieved (watchlist events) and their nature. Lacks output format details, but acceptable given no output schema exists and the tool's straightforward purpose.

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% (baseline 3). Description adds significant value by enumerating specific event type examples (funding, acquisitions, executive hires, contracts) that help populate the 'types' parameter, translating the schema's generic 'Comma-separated event types' into concrete business events.

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?

Specific verb 'Get' + resource 'events' + clear scope 'companies on your watchlist'. Lists concrete event categories (funding, acquisitions, etc.) that clarify return values. Mentions 'watchlist' which distinguishes from sibling 'get_events', though doesn't explicitly contrast them.

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?

No explicit guidance on when to use versus alternatives (e.g., get_events). No mention of prerequisites like requiring a populated watchlist first. Usage must be inferred from the name and 'watchlist' reference alone.

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