Skip to main content
Glama
yantrix-ai

@praveen030686/data-apis-mcp

Get Stock Financials

finance_stock_financials
Read-onlyIdempotent

Retrieve financial statements including income statements, balance sheets, and cash flow data for stock analysis. Powered by x402 USDC micropayments on Base.

Instructions

Get financial statements: income statement, balance sheet, and cash flow data. Costs $0.10 USDC per request via x402 on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock ticker (e.g., AAPL, MSFT, GOOGL)

Implementation Reference

  • Registration and implementation of the 'finance_stock_financials' tool. The handler calls the finance API endpoint /api/v1/stocks/financials/{symbol} and returns the data as text.
    server.registerTool(
      "finance_stock_financials",
      {
        title: "Get Stock Financials",
        description: `Get financial statements: income statement, balance sheet, and cash flow data.
    Costs $0.10 USDC per request via x402 on Base.`,
        inputSchema: {
          symbol: z.string().min(1).max(10).describe("Stock ticker (e.g., AAPL, MSFT, GOOGL)"),
        },
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      },
      async ({ symbol }) => {
        const data = await apiFetch(`${FINANCE_API}/api/v1/stocks/financials/${symbol.toUpperCase()}`);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds valuable behavioral context by disclosing the monetary cost per request ('Costs $0.10 USDC per request via x402 on Base'), which is critical operational information not captured in annotations. It doesn't contradict annotations and provides meaningful additional behavioral insight.

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 perfectly concise with two sentences that each earn their place: the first states the purpose and scope, the second discloses critical cost information. It's front-loaded with the core functionality and wastes no words. The structure efficiently communicates essential information without 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 moderate complexity (financial data retrieval), rich annotations covering safety and idempotency, and 100% schema coverage, the description is mostly complete. It adds crucial cost information that annotations don't capture. The main gap is the lack of output schema, but the description compensates by specifying what data types are returned (income statement, balance sheet, cash flow). It could be more complete by mentioning data freshness or format, but it's substantially adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage with a clear parameter description for 'symbol'. The tool description doesn't add any parameter-specific information beyond what the schema already provides. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no parameter information in the description, which applies here.

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 specific action ('Get financial statements') and resources ('income statement, balance sheet, and cash flow data'), distinguishing it from sibling tools like finance_stock_price (price only) or finance_stock_profile (company profile). It provides a precise verb+resource combination that leaves no ambiguity about what data is retrieved.

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 context through the cost disclosure ('Costs $0.10 USDC per request'), suggesting this should be used when financial statement data is needed and the cost is acceptable. However, it doesn't explicitly state when to use this tool versus alternatives like finance_stock_profile or finance_ai_report, nor does it provide exclusion criteria or prerequisites beyond the cost consideration.

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