Skip to main content
Glama
Fund-z

FundzWatch MCP Server

manage_watchlist

Add, remove, or list companies to track funding rounds, acquisitions, and executive hires, generating alerts for new business events.

Instructions

Add, remove, or list companies on your watchlist. Tracked companies generate alerts when they have new events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction: 'list' to view, 'add' to track, 'remove' to untrack
domainsNoCompany domains for add/remove (e.g., ['stripe.com', 'github.com'])

Implementation Reference

  • Implementation of the manage_watchlist tool, handling 'list', 'add', and 'remove' actions.
    case "manage_watchlist": {
      const action = (args as any).action;
      const domains = (args as any).domains;
    
      if (action === "list") {
        const data = await apiRequest("GET", "/watchlist");
        const companies = data.companies || [];
        if (companies.length === 0) {
          return textResult("Your watchlist is empty. Add companies with the 'add' action.");
        }
        const list = companies
          .map((c: any) => `- ${c.name || c.domain} (${c.domain})${c.matched ? "" : " [pending match]"}`)
          .join("\n");
        return textResult(`Watchlist (${data.total}/${data.limit} slots used):\n\n${list}`);
      }
    
      if (!domains || domains.length === 0) {
        return textResult("Please provide domains to add or remove.");
      }
    
      if (action === "add") {
        const data = await apiRequest("POST", "/watchlist", { domains });
        return textResult(
          `Added ${data.added} companies. Already tracked: ${data.already_tracked}. ` +
          `Not found: ${data.not_found}. Total tracked: ${data.total_tracked}.`
        );
      }
    
      if (action === "remove") {
        const data = await apiRequest("DELETE", "/watchlist", { domains });
        return textResult(`Removed ${data.removed} companies. Total tracked: ${data.total_tracked}.`);
      }
  • src/index.ts:127-148 (registration)
    Tool registration and schema definition for manage_watchlist.
    {
      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"],
      },
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the ongoing behavioral side effect (tracked companies generate alerts for new events), but lacks other behavioral details such as whether removal is permanent, if operations are idempotent, or any rate limiting.

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 efficient sentences with zero waste. The first front-loads the core CRUD functionality while the second explains the consequence (alerts), earning its place by justifying why the tool exists.

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?

Given the simple schema (2 params, 1 enum) and lack of output schema, the description is minimally adequate. It explains the watchlist concept and alert side-effect but omits details about return values or specific behavioral differences between the three actions.

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?

With 100% schema description coverage, the baseline is 3. The description mentions 'companies' which contextually maps to the 'domains' parameter, and references the action types, but does not add significant semantic detail (format constraints, required/optional logic per action) beyond what the schema already provides.

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?

Description clearly states the three supported operations (add, remove, list) and the target resource (companies on a watchlist). It also explains the value proposition (alert generation). It does not explicitly differentiate from the sibling `get_watchlist_events`, which is the main gap preventing a 5.

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?

The description explains what actions are possible (list, add, remove) but provides no guidance on when to choose this tool over siblings like `get_watchlist_events` or when to use each specific action vs. the others. No explicit when-to-use or when-not-to-use guidance is present.

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