Skip to main content
Glama
Fund-z

FundzWatch MCP Server

get_market_pulse

Retrieve a real-time market activity overview: funding totals, acquisition counts, executive moves, contracts, and product launches for the past 7 and 30 days.

Instructions

Get real-time market activity overview: funding totals, acquisition counts, executive moves, contracts, and product launches for the past 7 and 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the get_market_pulse tool. Calls GET /market/pulse API, then formats the response into a text summary including funding, acquisitions, executive moves, contracts, product launches counts for 7 and 30 days, plus largest funding rounds this week.
    case "get_market_pulse": {
      const data = await apiRequest("GET", "/market/pulse");
      const p = data.pulse;
      const text =
        `Market Pulse (as of ${p.generated_at}):\n\n` +
        `Funding: ${p.funding.count_7d} rounds this week (${p.funding.count_30d} this month), ` +
        `$${(p.funding.total_raised_7d / 1_000_000).toFixed(0)}M raised this week\n` +
        `Acquisitions: ${p.acquisitions.count_7d} this week (${p.acquisitions.count_30d} this month)\n` +
        `Executive Moves: ${p.executive_moves.count_7d} this week (${p.executive_moves.count_30d} this month)\n` +
        `Contracts: ${p.contracts.count_7d} this week (${p.contracts.count_30d} this month)\n` +
        `Product Launches: ${p.product_launches.count_7d} this week (${p.product_launches.count_30d} this month)\n\n` +
        `Largest Rounds This Week:\n` +
        (p.funding.largest_round || [])
          .map((r: any, i: number) => `  ${i + 1}. ${r.title} - $${(r.amount / 1_000_000).toFixed(1)}M`)
          .join("\n");
      return textResult(text);
    }
  • src/index.ts:113-119 (registration)
    Registration of the get_market_pulse tool in the ListToolsRequestSchema handler. Defines tool name, description, and inputSchema (empty object, no parameters required).
    {
      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: {} },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'real-time' but does not specify caching, rate limits, authentication requirements, or response structure. For a tool with zero annotations, more behavioral context is needed.

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?

A single sentence effectively front-loads the action and enumerates specific data categories and time frames. Every phrase earns its place with no extraneous information.

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?

For a simple tool with no parameters and no output schema, the description covers the data scope and time frames adequately. However, it omits response format details and does not differentiate from sibling tools like 'get_market_brief', which would help the agent decide when to use it.

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?

The tool has no parameters, and schema description coverage is 100% trivially. Baseline is 4 for zero-parameter tools. The description adds value by explaining the output categories and time frames, which goes beyond the empty schema.

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's purpose: 'Get real-time market activity overview' and specifies the categories (funding totals, acquisition counts, etc.) and time frames (past 7 and 30 days). This distinguishes it from siblings like 'get_events' or 'get_market_brief' which likely focus on different aspects.

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?

The description implies usage for a broad market overview, but does not explicitly state when to use this tool versus alternatives like 'get_market_brief' or 'get_events'. No exclusions or prerequisites are provided, leaving the agent to infer context.

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