Skip to main content
Glama
yantrix-ai

@praveen030686/data-apis-mcp

Get Market Overview

finance_market_overview
Read-onlyIdempotent

Access real-time global market data including major stock indices (S&P 500, NASDAQ, FTSE 100), commodities (Gold, Oil), and Treasury yields for financial analysis and decision-making.

Instructions

Get global market overview: S&P 500, Dow Jones, NASDAQ, FTSE 100, Nikkei 225, DAX, plus Gold, Silver, Oil, and Treasury yields. Costs $0.05 USDC per request via x402 on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the finance_market_overview tool, which fetches market overview data from the finance API.
    async () => {
      const data = await apiFetch(`${FINANCE_API}/api/v1/market/overview`);
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • src/index.ts:232-240 (registration)
    Registration of the finance_market_overview tool in the MCP server.
    server.registerTool(
      "finance_market_overview",
      {
        title: "Get Market Overview",
        description: `Get global market overview: S&P 500, Dow Jones, NASDAQ, FTSE 100, Nikkei 225, DAX, plus Gold, Silver, Oil, and Treasury yields.
    Costs $0.05 USDC per request via x402 on Base.`,
        inputSchema: {},
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      },
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: it specifies the exact assets covered (e.g., major indices, commodities, yields) and discloses the cost ($0.05 USDC per request via x402 on Base), which are critical for usage decisions. No contradiction with annotations exists.

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 highly concise and front-loaded: the first sentence defines the scope (global market overview with specific examples), and the second sentence adds essential operational details (cost and payment method). Every sentence earns its place with no wasted words or redundancy.

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 the tool's simplicity (0 parameters, rich annotations covering safety and behavior), the description is reasonably complete. It specifies the assets returned and cost, which are crucial for this type of data-fetching tool. However, without an output schema, it could benefit from mentioning the format or structure of the returned data (e.g., JSON with fields), leaving a minor gap.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, maintaining focus on the tool's purpose and cost. A baseline of 4 is applied for zero-parameter tools, as the description compensates by providing other relevant information.

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?

The description clearly states the tool retrieves a 'global market overview' and lists specific financial instruments (S&P 500, Dow Jones, NASDAQ, FTSE 100, Nikkei 225, DAX, Gold, Silver, Oil, Treasury yields). It distinguishes from siblings like finance_stock_price or finance_forex_rate by covering multiple asset classes. However, it doesn't explicitly contrast with finance_ai_report or finance_stock_financials, which prevents a perfect score.

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 guidance on when to use this tool versus alternatives. It doesn't mention when this overview is preferable to individual price tools (e.g., finance_stock_price for single stocks) or more specialized tools (e.g., finance_stock_financials for detailed analysis). The cost information is operational but doesn't inform selection among siblings.

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/yantrix-ai/x402-apis-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server