Skip to main content
Glama

Market Intelligence API (core)

Fundamentals batch

stocks.fundamentals
Read-onlyIdempotent

Fundamentals of up to 10 US-listed companies in one call ($0.10): per ticker revenue, earnings, margins, growth, balance sheet and a fundamental signal from SEC filings.

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": {
      "symbols": "<symbols>"
    },
    "name": "stocks.fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesUS tickers, e.g. ["AAPL", "MSFT"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds value beyond that by disclosing the per-call price ($0.10), the data provenance (SEC filings), and the per-ticker content returned — though it says nothing about behavior for unknown/foreign tickers or partial failures.

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?

A single front-loaded sentence that packs scope, cost, and return contents with no filler or preamble. Every clause carries information an agent needs before calling.

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?

For a one-parameter tool with no output schema, the description does the essential work of enumerating the return fields and the batch ceiling. Minor gaps remain around error handling and whether the fundamental signal is a rating or raw figure, but nothing critical to calling it correctly is missing.

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?

With a single parameter at 100% schema description coverage, the schema already documents the ticker array, its item format, and the 10-item cap. The description only restates the batch limit and adds the 'US-listed' constraint, which the schema's 'US tickers' description largely covers, so it contributes little new parameter meaning.

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 names a concrete resource (fundamentals: revenue, earnings, margins, growth, balance sheet, SEC-filing signal) and a precise scope (up to 10 US-listed tickers per call). It clearly is not a price/quote or news tool, but it never names or contrasts a sibling, so differentiation is inferred from the payload list rather than stated.

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?

Usage is only implied: 'in one call' conveys that this is the batch path for a handful of tickers, and the 10-ticker ceiling hints at splitting larger lists. There is no explicit when-to-use, when-not-to-use, or pointer to which sibling to call for price, news, or macro context instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources