Skip to main content
Glama
Fund-z

FundzWatch MCP Server

get_market_pulse

Monitor real-time market activity including funding totals, acquisitions, executive moves, contracts, and product launches over 7 and 30-day periods to track business events and generate strategic insights.

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

  • The handler for "get_market_pulse" performs an API request to /market/pulse and formats the returned data into a text report.
    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:114-119 (registration)
    Registration of the "get_market_pulse" tool within the listTools handler.
      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: {} },
    },
Behavior3/5

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

With no annotations, description carries full disclosure burden. Adds valuable behavioral constraints: 'real-time' indicates data freshness, and 'past 7 and 30 days' defines fixed, non-configurable lookback windows. However, omits permissions, rate limits, and error conditions typically expected for unannotated tools.

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 and resource. Efficiently enumerates data categories and timeframes without redundancy. Every element earns its place.

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?

Comprehensive for a parameterless tool. Compensates for missing output schema by enumerating specific return data categories and temporal scope. Adequate for tool complexity, though could optionally note data aggregation level.

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?

Input schema has zero parameters. Per scoring rules, zero-parameter tools receive baseline 4. Description appropriately requires no parameter clarification.

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?

Provides specific verb ('Get'), resource ('market activity overview'), and detailed scope including specific metrics (funding totals, acquisition counts, executive moves, contracts, product launches) and fixed timeframes (past 7 and 30 days). Clear about what the tool retrieves, though lacks explicit differentiation from similar sibling 'get_market_brief'.

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?

Lists specific content categories providing implied usage context for when this aggregated data is needed, but lacks explicit when/when-not guidance or named alternative tools (e.g., when to use 'get_market_brief' or 'get_events' instead).

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