Fintel Discovery — Financial Intelligence for AI Agents

Lookup Ticker Symbol by Name

LookupTicker

Read-onlyIdempotent

    Search for a Yahoo Finance ticker symbol by company name, fund name,
    or keyword. Returns matching symbols with exchange and asset type.
    Use this when you have a name but need the ticker symbol.

    Use this tool when:
    - You know a company name but not its ticker symbol
    - You want to find the ticker for a specific ETF or mutual fund
    - You are disambiguating between similarly named securities

    asset_type options: 'stock', 'etf', 'mutualfund', 'index',
    'cryptocurrency', 'currency', 'future', 'all'.

    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.2/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond that: it is backed by Yahoo Finance/yfinance, requires no API key, and returns exchange/asset type information. This gives the agent useful expectations about data source and result shape.

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 compact and front-loaded: opening purpose, then use cases, then an options list, then source/auth note. Every sentence adds useful information without unnecessary filler.

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?

For a read-only lookup tool with an output schema, the description covers purpose, use cases, key parameter options, and authentication requirements. It could additionally clarify result limiting/pagination or mention that only symbol metadata is returned, but nothing critical is missing for correct invocation.

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 description explains the core query behavior and enumerates valid asset_type options, which helps selection. However, it does not address max_results or the various framework parameters present in the schema, and the context signal indicates low schema_description_coverage, so the description only partially compensates for parameter documentation.

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: 'Search for a Yahoo Finance ticker symbol by company name, fund name, or keyword.' It also states what is returned ('matching symbols with exchange and asset type'), and the use cases clearly distinguish it from the many sibling search/data tools.

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 provides explicit when-to-use scenarios: finding a ticker from a name, locating ETF/mutual fund tickers, and disambiguating similarly named securities. It does not name alternative sibling tools or give when-not-to-use guidance, 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?