Fintel Discovery — Financial Intelligence for AI Agents

Get Ticker Info & Profile

GetTickerInfo

Read-onlyIdempotent

    Fetch the full Yahoo Finance profile for a stock, ETF, mutual fund, crypto,
    or index. Returns name, sector, industry, market cap, P/E ratio, 52-week
    range, beta, dividend yield, description, and 60+ other metadata fields.

    Use this tool when:
    - You need a quick summary of what a company or fund is and its valuation
    - You want sector/industry classification for a ticker
    - You need current price metadata like market cap, float, or short ratio

    Works for: stocks (AAPL), ETFs (SPY), mutual funds (VFINX),
    crypto (BTC-USD), indices (^GSPC), forex (EURUSD=X).

    Source: Yahoo Finance via yfinance. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false, reducing the burden on the description. The description adds useful behavioral context by naming the data source (Yahoo Finance via yfinance), noting that no API key is required, and clarifying that the tool accepts multiple instrument types. It does not discuss rate limits or data freshness, but those are less critical given the annotations.

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 well-structured and front-loaded with a scoping first sentence, followed by a useful when-to-use bullet list and a compact supported-assets line. Every sentence adds information without filler or redundancy.

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?

Since an output schema exists, the description does not need to explain return values, and it already covers purpose, use cases, supported instrument types, and data source/auth expectations. The main gaps are that it does not explicitly explain how to provide the symbol parameter or when to prefer a sibling tool like LookupTicker or GetFundProfile. Overall, it is sufficiently complete for most correct invocations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Context signals indicate 0% schema description coverage and only one top-level parameter, so the description must compensate for parameter explanation. It only implies the symbol parameter through asset-type examples like AAPL, SPY, and BTC-USD, and never explicitly states that a symbol must be provided or how the top-level 'params' object is used. Several schema fields such as mcp_prompt_id, wholesaler_ids, and exclude_fillers are not tied to this tool's purpose.

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 opens with a specific verb and resource: 'Fetch the full Yahoo Finance profile' and enumerates concrete return fields such as market cap, P/E ratio, 52-week range, and dividend yield. It clearly distinguishes this metadata/profile tool from price-history, ratings, or filings siblings by emphasizing the profile focus and 60+ metadata fields. The asset-type list makes the tool's scope 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 includes an explicit 'Use this tool when' section with three concrete scenarios: quick company/fund summary, sector/industry classification, and price metadata needs. It does not explicitly say when not to use it or name sibling alternatives such as LookupTicker or GetFundProfile, so it stops short of a 5.

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

All Fintel Discovery — Financial Intelligence for AI Agents tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools target a distinct resource and action, with clear separation between search and detail tools (e.g., SearchIAPDFirm vs GetIAPDFirmDetail, SearchBrokerCheck vs GetBrokerCheckDetail). A few pairs like SearchBrokerCheck and SearchBrokerCheckFirm could cause momentary confusion, but descriptions clarify individual vs firm scope.

Naming Consistency4/5

The dominant pattern is consistent: Search* for discovery, Get* for retrieval, with CamelCase throughout. Minor deviations like LookupTicker and MapInstrumentIds introduce different verbs, and SearchBrokerCheck does not explicitly signal 'individual' unlike SearchBrokerCheckFirm, but the overall convention remains predictable.

Tool Count2/5

With 32 tools, the surface is quite heavy and exceeds the 25+ threshold for 'too many.' While the financial intelligence domain is broad, several search/detail pairs and overlapping data-source tools could be consolidated to reduce cognitive load for agents.

Completeness4/5

The toolset covers major workflows well: 13F holdings, fund fee comparison, advisor due diligence, macro data, price history, options, and identifier mapping. Minor gaps exist, such as no standalone real-time quote tool, no news/sentiment data, and no direct CUSIP-to-company-name search, but these are workable around.

Resources

Need Help?