Skip to main content
Glama
rezmeplxrf

InsightSentry MCP

by rezmeplxrf

get_fundamentals_series

Retrieve historical time series data for up to 5 fundamental indicators per request. Access financial metrics like earnings, revenue, and valuation ratios by symbol to analyze company performance trends and track financial history.

Instructions

Fundamental Data in Time Series format. Retrieve historical data for specific indicators. A maximum of 5 Indicator IDs can be requested at a time. The list of available Indicator IDs is provided in the fundamental_series and technical_series fields of the /v3/symbols/fundamentals endpoint. Some parameters may not apply to certain Indicator IDs, and not all indicators are supported for every symbol. → Returns {code: string, total_items: number, last_update: number, data: [{id: string, name: string, data: [{time: number, close: number}]}]} — max 5 indicator IDs per request. If you don't know the available IDs, call get_fundamentals_meta or get_symbol_fundamentals first — both return field objects with {id, name, category} that you can use here. Not all indicators are available for every symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSymbol in Exchange:Symbol format (e.g., NASDAQ:AAPL, NYSE:TSLA). You can search for this symbol code using the /v3/symbols/search endpoint.
idsYes(Required) Comma-separated list of indicator IDs (maximum 5). Available IDs can be retrieved from /v3/symbols/fundamentals endpoint's 'fundamental_series' and 'technical_series' fields.
filterNo(Optional) JSONata expression to filter/transform the API response server-side before it reaches you. Use this to extract only the fields or rows you need, reducing token usage. See https://jsonata.org for syntax.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the return structure (code, total_items, data array) since no output schema exists, notes the max 5 indicator constraint, and warns that 'some parameters may not apply to certain Indicator IDs.' Deducted one point for omitting rate limits or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Contains redundant repetition: 'A maximum of 5 Indicator IDs' appears twice, and 'not all indicators are available for every symbol' is restated. The arrow notation '→ Returns' is informal. However, all content serves the agent's understanding despite the redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Excellent compensation for missing output schema by detailing the return JSON structure inline. Given no annotations and no output schema, the description provides prerequisites, constraints, return format, and sibling relationships—everything needed for correct invocation.

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?

Schema coverage is 100%, establishing baseline 3. Description adds value by explaining the dependency workflow for the 'ids' parameter (must fetch valid IDs from sibling endpoints first) and noting parameter interaction edge cases ('some parameters may not apply to certain Indicator IDs').

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?

Opens with resource type ('Fundamental Data in Time Series format') and specific action ('Retrieve historical data for specific indicators'). Explicitly distinguishes from siblings get_fundamentals_meta and get_symbol_fundamentals by stating this tool requires pre-existing Indicator IDs while those provide the ID catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit prerequisite workflow: 'If you don't know the available IDs, call get_fundamentals_meta or get_symbol_fundamentals first.' Also clarifies constraints that govern when the tool works ('not all indicators are available for every symbol') and parameter applicability limits.

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/rezmeplxrf/insight_mcp'

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