Skip to main content
Glama
finimpulse

FinImpulse MCP Server

by finimpulse

get_search_lite

Search unified results for stocks, ETFs, and mutual funds, returning core identification, current pricing, and key performance metrics. Filter, sort, and paginate to refine matches.

Instructions

Returns a unified, cross-asset search result for stocks, ETFs, and mutual funds with a focused field set covering core identification, current pricing, and key performance metrics. The response field set is fixed, but it is possible to control which fields are included through the select_identifiers parameter. For a comprehensive field set use the /v1/search endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoUser-defined request identifier.
limitNoMaximum number of matched items returned.
offsetNoPagination offset (0-based).
filtersNoOptional filter expressions. Each filter condition is defined as: [field, operator, value]. Conditions can be combined using logical operators and/or. Supported operators: Numeric fields: > - greater than >= - greater than or equal < - less than <= - less than or equal = - equals <> - not equal String fields: like – pattern match (requires % as a wildcard) not_like - pattern does not match (requires % as a wildcard) contains - value exists in string not_contains - value does not exist in string startswith - string starts with value endswith - string ends with value % usage examples: %abc% - matches any string containing "abc" abc% - matches any string starting with "abc" %abc - matches any string ending with "abc" Example: "filters": [ "short_name", "contains", "Market" ]
sort_byNoOptional sorting configuration for result items. Each sorting setup is defined as [selector, desc]: selector - Metric used for sorting (e.g., amount_usd). desc - Sorting direction (true for descending, false for ascending). Sortings can be combined using ,. Example: { "selector": "amount_usd", "desc": true }
symbolsNoA list of ticker symbols to retrieve. When provided, the response returns only the specified tickers. If a symbol does not exist, it is excluded from the results.
quote_typesNoControls which asset types are included in the search. If none are provided, all supported asset types are returned.
search_textNoFree-text query (e.g., “NVDA”, “NVIDIA”, partial ticker, partial name).
select_identifiersNoA list of field names to include in the response. When provided, each item in the response contains only the specified fields. When not provided or set to null, the full field set is returned. "symbol" and "logo" are always returned regardless of the value passed.
has_public_financial_reportsNoIndicates whether the company provides public financial statements.
hide_tickers_with_company_nameNoExclude tickers with available names. true - exclude tickers with a company/fund name; false - include tickers with a company/fund name.
show_tickers_without_company_nameNoInclude tickers with missing names. true - include tickers even if the company/fund name is missing; false - exclude tickers without a company/fund name.
Behavior3/5

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

The description discloses that the response field set is fixed but controllable via select_identifiers and characterizes the output as including core identification, pricing, and performance metrics. With no annotations, it does not explicitly state read-only behavior or error semantics, but the search context makes this implicit. The added context about the fixed field set and the alternative endpoint provides some value but not deep behavioral detail.

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?

Two sentences with no redundancy. The main purpose and the key alternative are stated upfront, making the description concise and well-structured.

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

Completeness3/5

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

For a tool with 12 parameters, no output schema, and no annotations, the description gives a high-level overview but omits mention of filtering, sorting, pagination, and other capabilities. The schema fills many gaps, but the lack of a defined output structure means the agent must infer the response shape from the brief mention of 'core identification, current pricing, and key performance metrics'.

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?

The input schema provides 100% coverage of all 12 parameters with detailed descriptions, so the baseline is 3. The description adds a note about select_identifiers controlling the field set, but this largely repeats schema information. No additional parameter semantics are provided beyond the schema.

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 returns 'a unified, cross-asset search result for stocks, ETFs, and mutual funds' and distinguishes it from the sibling 'get_search' by emphasizing a 'focused field set' and redirecting to '/v1/search' for comprehensive needs. The verb and resource are specific and unambiguous.

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

Usage Guidelines4/5

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

The description explicitly names an alternative endpoint for comprehensive field sets ('For a comprehensive field set use the /v1/search endpoint'), implying this tool is intended for focused searches. However, it does not provide broader when-to-use/when-not-to-use guidance beyond this single distinction.

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/finimpulse/mcp-server-typescript'

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