Skip to main content
Glama

XFINLAB Intelligence

by com.xfinlab
OverviewDiscussionsAdmin

get_global_market_map

Get a cross-region global market snapshot ('World Engine'): macro indicators (GDP growth/inflation/unemployment, with source attribution -- world_bank/fred/ecb), filtered regional headlines, and FinBERT sentiment for each requested region, plus a top-level global headlines feed (GDELT). Regions: us, europe, japan, korea, china, hk, tw, sea, me, latam. No AI narrative, no directional signal -- structured real data only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoXFINLAB Intelligence API key (X-API-Key). Omit if supplied via HTTP header instead.
regionsNoComma-separated region keys, e.g. 'us,hk,china'. Omit for all 10 regions.
news_limitNoHeadlines per region, 1-20.
include_sentimentNoWhether to run FinBERT sentiment on each region's headlines.
marketplace_license_keyNoOptional: an mcp-marketplace.io license key for this listing's paid tier. If valid, upgrades a free XFINLAB API key's daily quota to Pro for this call. Omit if supplied via the X-Marketplace-License-Key header instead, or if not using a marketplace license.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / marketplace_license_key
      Added value: +{
+  "description": "Optional: an mcp-marketplace.io license key for this listing's paid tier. If valid, upgrades a free XFINLAB API key's daily quota to Pro for this call. Omit if supplied via the X-Marketplace-License-Key header instead, or if not using a marketplace license.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
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 of behavioral disclosure. It does disclose that the tool returns structured real data only and does not generate AI narrative or directional signal, which is valuable context. However, it omits any mention of side effects (though likely read-only), auth requirements beyond the schema, rate limits, or error behavior. It partially compensates but not fully.

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?

The description is a single, reasonably sized paragraph. It front-loads the primary purpose, then details content types, lists regions, and ends with a caveat about no AI narrative. Every sentence contributes unique information; there is no filler or repetition. It could be slightly tighter, but it is well structured.

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?

Given that there is no output schema, the description does a solid job of conveying what the agent can expect: macro indicators with source attribution, regional headlines, FinBERT sentiment, and a global headlines feed. It also enumerates valid regions. It does not mention pagination, output formatting, or error handling, but the key functional coverage is present for an agent to invoke the tool 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?

The schema already describes all parameters with 100% coverage, so baseline is 3. The description adds value by enumerating the exact region keys (us, europe, japan, korea, china, hk, tw, sea, me, latam), which the schema does not list. It also clarifies the meaning of 'regions' in context. This extra enumeration is genuinely useful for an agent constructing a call.

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 a specific verb ('Get'), a precise resource ('cross-region global market snapshot'), and enumerates the exact content: macro indicators with source attribution, regional headlines, FinBERT sentiment, and a global headlines feed. It also explicitly excludes AI narrative and directional signal, which implicitly differentiates it from sibling tools like get_sentiment or get_technical_analysis. The scope is unambiguous.

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 provides no explicit guidance on when to use this tool versus its siblings. It does not name alternatives or state conditions for choosing this over get_sentiment, get_intelligence_feed, or get_market_events. The implicit 'structured real data only' hint is not sufficient for an agent to route correctly among the five siblings.

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

All XFINLAB Intelligence toolsInspect
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.

Resources