tradingview-finance MCP Server

Overview Schema Source Related Servers Discussions Admin

get_documents

Retrieve SEC filings (10-K, 10-Q, 8-K) and earnings call transcripts for a stock symbol. Access public corporate reports.

Instructions

Get public corporate report documents, SEC filings (10-K, 10-Q, 8-K), and earnings call transcripts.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_documents"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	The stock symbol, e.g. "NASDAQ:AAPL".

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not mention side effects, access restrictions, rate limits, or pagination behavior. The description only states the tool's purpose without revealing operational details.

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 a single sentence that is direct and to the point, with no unnecessary words. It is front-loaded with the verb and key types of documents.

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 low complexity (one parameter, output schema present), the description provides the essential context of document types. However, it lacks details on potential limitations like date range or supported exchanges. Still, it is largely complete for a simple retrieval tool.

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% for the single parameter 'symbol,' which already provides a clear description. The tool description does not add any additional meaning beyond what the schema offers. Baseline score of 3 is appropriate given schema coverage.

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 tool retrieves 'public corporate report documents, SEC filings (10-K, 10-Q, 8-K), and earnings call transcripts,' specifying both the verb and resource. It distinguishes itself from sibling tools (e.g., get_news, get_earnings_calendar) by focusing on documents rather than other financial data types.

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 explains what the tool retrieves but does not provide explicit guidance on when to use it over alternatives. There is no mention of prerequisites, exclusions, or when not to use it. Usage is implied by the document types listed.

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