Skip to main content
Glama
Fund-z

FundzWatch MCP Server

get_usage

Retrieve your FundzWatch API usage details: calls made, current limits, and active tier. Stay informed about your plan consumption.

Instructions

Check your FundzWatch API usage: calls made, limits, current tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration (schema + description) for the 'get_usage' tool. Defined in the tools list with name, description, and empty inputSchema (no parameters required).
    {
      name: "get_usage",
      description: "Check your FundzWatch API usage: calls made, limits, current tier.",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • Handler for the 'get_usage' tool. Makes a GET request to '/usage' API endpoint and formats the response showing tier, API calls used/limit, AI score calls used/limit, and last API call timestamp.
    case "get_usage": {
      const data = await apiRequest("GET", "/usage");
      const text =
        `FundzWatch Usage (${data.current_period}):\n\n` +
        `Tier: ${data.tier}\n` +
        `API Calls: ${data.api_calls_used} / ${data.limits.api_calls_monthly}\n` +
        `AI Score Calls: ${data.ai_score_calls_used} / ${data.limits.ai_score_calls_monthly}\n` +
        (data.last_api_call ? `Last API Call: ${data.last_api_call}` : "");
      return textResult(text);
    }
  • src/index.ts:71-168 (registration)
    The 'get_usage' tool is registered as part of the tools array in the ListToolsRequestSchema handler, and its case handler is included in the CallToolRequestSchema switch statement.
    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: {} },
        },
      ],
    }));
  • The apiRequest helper function is used by the get_usage handler to make the GET request to the /usage API endpoint.
    async function apiRequest(
      method: string,
      path: string,
      params?: Record<string, any>
    ): Promise<any> {
      const apiKey = getApiKey();
      const url = new URL(`${API_BASE}${path}`);
    
      const options: RequestInit = {
        method,
        headers: {
          Authorization: `Bearer ${apiKey}`,
          "Content-Type": "application/json",
          "User-Agent": "fundzwatch-mcp/1.0.1",
        },
      };
    
      if (method === "GET" && params) {
        Object.entries(params).forEach(([key, value]) => {
          if (value !== undefined && value !== null) {
            url.searchParams.append(key, String(value));
          }
        });
      } else if (method !== "GET" && params) {
        options.body = JSON.stringify(params);
      }
    
      const response = await fetch(url.toString(), options);
    
      if (!response.ok) {
        const errBody: any = await response.json().catch(() => ({ message: response.statusText }));
        throw new Error(`API error ${response.status}: ${errBody.message || errBody.error || response.statusText}`);
      }
    
      return response.json();
    }
  • The textResult helper formats the response as a text content block, used by get_usage to return the formatted usage string.
    function textResult(text: string) {
      return { content: [{ type: "text" as const, text }] };
    }
Behavior4/5

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

With no annotations, the description carries the burden. It explains the tool returns calls made, limits, and tier, implying read-only behavior. It does not mention side effects or authentication, but for a simple check tool this is adequate.

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?

The description is a single sentence of 10 words, front-loaded with the action, and every word adds value. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, no output schema, and no annotations, the description is fully complete. It explains what the tool returns (calls made, limits, current tier).

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% with no parameters. The description adds no parameter info, but none is needed. Baseline 4 is appropriate.

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?

The description clearly states the tool checks FundzWatch API usage (calls, limits, tier). It uses a specific verb (Check) and resource (API usage), distinguishing it from sibling tools which cover events, market data, etc.

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?

The description implies the tool is used to check API usage, but does not explicitly state when to use it versus alternatives. However, siblings are unrelated, so no confusion arises.

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