FinzData market data

Get global activity data (shipping, ports, air, road)

get_global_pulse

Read-onlyIdempotent

Answers 'how busy is the Suez Canal (or Singapore port, or US airspace) right now?' Give a dataset (chokepoints, ports, port_calls, air, air_europe, air_us or road); optionally match to filter by name or id (e.g. Suez, Singapore, JFK) and dim for air data. Returns daily real-world activity that leads the official statistics: ship transits through 28 chokepoints since 2019, port calls and estimated imports/exports for 2,000+ ports, daily flights by airport, airline, country and region, US flights, cancellations and delays since 1987, and toll and congestion-zone traffic. Taiwan and Korea chip exports are macro series - use get_macro_vintage for those.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset": "<dataset>"
    },
    "name": "get_global_pulse"
  }
}

Input Schema

Name	Required	Description
`dim`	No	For air/air_us: airport, airline, country or region.
`end`	No
`as_of`	No	Point-in-time cutoff (YYYY-MM-DD). Nothing dated after this is returned, preventing look-ahead bias. Defaults to today (UTC).
`match`	No	Name or id filter, e.g. Suez Canal, Singapore, JFK, US.
`start`	No
`dataset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, so the bar is lower; the description still adds that results are daily and lead official statistics, plus the specific coverage per dataset (28 chokepoints since 2019, 2,000+ ports, US flights since 1987). It does not discuss rate limits or response shape, but the temporal coverage disclosure is genuinely useful context beyond the annotations.

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?

Front-loads the user-facing question, then moves to parameters, then to return coverage, then the sibling redirect — a sensible order with no filler sentences. The dataset-coverage clause is long and dense, but each enumeration adds distinguishing information rather than padding.

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?

With no output schema, the description must explain returns, and it does so in concrete terms (transits, port calls, estimated imports/exports, flights, cancellations, delays, toll/congestion traffic). Combined with the dataset routing and the point-in-time note already in the schema, an agent has enough to select and call this correctly.

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 only 50% (start/end are undocumented), so the description carries real weight: it explains the dataset enum contents, gives concrete match examples (Suez, Singapore, JFK) and scopes dim to air/air_us. start and end remain unexplained in both places, which keeps it below a 5.

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?

Opens with the concrete question it answers ('how busy is the Suez Canal... right now?') and states the specific resource: daily real-world activity across chokepoints, ports, port calls, air and road. It explicitly carves out chip-export macro series and routes them to get_macro_vintage, so an agent can distinguish it from that sibling without opening either schema.

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?

Gives clear when-to-use framing (real-time activity vs official statistics) and an explicit alternative for the chip-export case ('use get_macro_vintage for those'). It does not address other plausible alternatives such as get_events or get_macro_vintage generally, but the routing guidance present is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FinzData market data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.