Skip to main content
Glama
Fund-z

FundzWatch MCP Server

get_watchlist_events

Retrieve recent funding, acquisitions, executive hires, and contracts for companies on your watchlist. Filter events by time range and event type.

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

  • Tool schema registration for 'get_watchlist_events' defining name, description, and input schema (days and types params).
    {
      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" },
        },
      },
    },
  • Handler implementation for 'get_watchlist_events' that calls GET /watchlist/events API and formats the response into a text summary with event details.
    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}`);
    }
  • src/index.ts:71-168 (registration)
    Tool registration via ListToolsRequestSchema handler, where the 'get_watchlist_events' tool is registered alongside other tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: "get_scored_leads",
          description:
            "Get AI-scored sales leads based on your ICP (Ideal Customer Profile). " +
            "Returns companies with recent business events scored by AI for buyer intent, " +
            "buying stage, and recommended outreach strategy.",
          inputSchema: {
            type: "object" as const,
            properties: {
              min_score: { type: "number", description: "Minimum buyer intent score (0-100). Default: 0" },
              max_results: { type: "number", description: "Max leads to return (1-50). Default: 25" },
              buying_stages: {
                type: "array",
                items: { type: "string" },
                description: "Filter by buying stage: 'Active Evaluation', 'Decision', 'Research', 'Awareness'",
              },
              industries: {
                type: "array",
                items: { type: "string" },
                description: "Filter by industry (e.g., ['SaaS', 'HealthTech', 'FinTech'])",
              },
            },
          },
        },
        {
          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" },
            },
          },
        },
        {
          name: "get_market_pulse",
          description:
            "Get real-time market activity overview: funding totals, acquisition counts, " +
            "executive moves, contracts, and product launches for the past 7 and 30 days.",
          inputSchema: { type: "object" as const, properties: {} },
        },
        {
          name: "get_market_brief",
          description:
            "Get today's AI-generated strategic intelligence brief with narrative analysis " +
            "of the most important market movements, patterns, and opportunities.",
          inputSchema: { type: "object" as const, properties: {} },
        },
        {
          name: "manage_watchlist",
          description:
            "Add, remove, or list companies on your watchlist. Tracked companies generate " +
            "alerts when they have new events.",
          inputSchema: {
            type: "object" as const,
            properties: {
              action: {
                type: "string",
                enum: ["list", "add", "remove"],
                description: "Action: 'list' to view, 'add' to track, 'remove' to untrack",
              },
              domains: {
                type: "array",
                items: { type: "string" },
                description: "Company domains for add/remove (e.g., ['stripe.com', 'github.com'])",
              },
            },
            required: ["action"],
          },
        },
        {
          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" },
            },
          },
        },
        {
          name: "get_usage",
          description: "Check your FundzWatch API usage: calls made, limits, current tier.",
          inputSchema: { type: "object" as const, properties: {} },
        },
      ],
    }));
Behavior2/5

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

No annotations provided, so description carries full burden. Only lists event types; no mention of rate limits, data freshness, empty results behavior, or whether tool is read-only.

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?

Single sentence, front-loaded with core information. Concise but could be structured with bullet points for clarity.

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?

Adequate context for a simple tool with no output schema and low parameter count. Describes scope and examples, but missing return format.

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% with descriptions for both 'days' and 'types'. Description adds event type examples but no additional meaning beyond schema. 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?

Clear verb ('Get'), resource ('recent events for companies on your watchlist'), and specific examples (funding, acquisitions, executive hires, contracts). Distinguishes from sibling tools like 'get_events' by scoping to watchlist.

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

Usage Guidelines3/5

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

Implies usage for watchlist events but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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