Skip to main content
Glama
yantrix-ai

@praveen030686/data-apis-mcp

Get Stock News

finance_stock_news
Read-onlyIdempotent

Retrieve recent news articles for any stock ticker with titles, publishers, links, and thumbnails to monitor market developments and company updates.

Instructions

Get latest 10 news articles for any stock including title, publisher, link, and thumbnail. Costs $0.05 USDC per request via x402 on Base.

Input Schema

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

Implementation Reference

  • The handler function for 'finance_stock_news' that fetches news data for a given stock symbol.
    async ({ symbol }) => {
      const data = await apiFetch(`${FINANCE_API}/api/v1/stocks/news/${symbol.toUpperCase()}`);
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • src/index.ts:178-193 (registration)
    Registration of the 'finance_stock_news' tool including title, description, and input schema.
    server.registerTool(
      "finance_stock_news",
      {
        title: "Get Stock News",
        description: `Get latest 10 news articles for any stock including title, publisher, link, and thumbnail.
    Costs $0.05 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/news/${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 cover read-only, non-destructive, idempotent, and open-world behavior. The description adds valuable context beyond annotations: it discloses the cost ('Costs $0.05 USDC per request via x402 on Base') and specifies the exact number of articles returned ('latest 10'), which are not captured in annotations. 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 extremely concise and front-loaded, consisting of only two sentences that efficiently convey purpose, output details, and cost. Every word serves a clear purpose, with no redundant or unnecessary information, making it easy for an agent to parse quickly.

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 low complexity (1 parameter, no output schema) and rich annotations, the description is mostly complete. It covers purpose, output format, and cost, but lacks details on error handling or response structure. However, for a simple read-only tool with good annotations, this is sufficient for effective agent use.

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?

Schema description coverage is 100%, with the parameter 'symbol' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding.

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 latest 10 news articles') and resource ('for any stock'), distinguishing it from sibling tools like finance_stock_price or finance_stock_financials. It specifies the exact output format ('including title, publisher, link, and thumbnail'), making the purpose unambiguous.

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 by specifying 'latest 10 news articles' and mentioning a cost, but it does not explicitly state when to use this tool versus alternatives like finance_ai_report or finance_market_overview. No exclusions or prerequisites are provided, leaving the agent to infer appropriate scenarios.

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