Skip to main content
Glama
rezmeplxrf

InsightSentry MCP

by rezmeplxrf

get_fundamentals_meta

Discover financial field schemas and definitions to identify balance sheet, cash flow, and valuation metrics before querying specific stock fundamentals.

Instructions

Meta data for /fundamentals endpoints. Retrieve the fundamentals schema and metadata. This endpoint returns the layout and definitions only — it does not include actual data, which are provided by /v3/symbols/{symbol}/fundamentals. → Returns {last_update: number, base: [{id: string, name?: string, category?: string, group?: string, type?: string, period?: string}], fundamental_series: [{id: string, name: string}], technical_series: [{id: string, name: string}]}. No values — schema only. Use this to discover and search available fields when you're unsure which field IDs exist (e.g., find cash flow fields, balance sheet metrics, valuation ratios) by scanning names and categories. Then call get_symbol_fundamentals with a specific symbol and filter its response to only the IDs you identified here. Use fundamental_series/technical_series IDs with get_fundamentals_series for historical data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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?

With no annotations provided, the description carries full disclosure burden. It successfully documents the return structure inline (last_update, base, fundamental_series objects), clarifies 'No values — schema only,' and implies read-only behavior. Minor gap: doesn't explicitly state idempotency or caching characteristics.

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

Conciseness4/5

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

Information-dense and front-loaded with purpose. The inline JSON return structure is compressed but functional. Examples (e.g., 'find cash flow fields, balance sheet metrics') efficiently communicate use cases. Slightly dense but every sentence serves tool selection or invocation.

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?

Despite no formal output schema, the description comprehensively documents return values inline. Combined with clear sibling differentiation and discovery workflow examples, it provides complete context for an agent to use this metadata discovery tool effectively.

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 coverage is 100% with the 'filter' parameter fully documented as a JSONata expression. The description adds no explicit parameter guidance, but none is needed given complete schema documentation, warranting the baseline score.

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 explicitly states the tool retrieves 'the fundamentals schema and metadata' and clearly distinguishes it from siblings by specifying it returns 'layout and definitions only' and 'does not include actual data, which are provided by /v3/symbols/{symbol}/fundamentals' (get_symbol_fundamentals).

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 workflow guidance: 'Use this to discover and search available fields when you're unsure which field IDs exist... Then call get_symbol_fundamentals...' and references get_fundamentals_series for historical data, creating a clear decision tree for agent tool selection.

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