MetricDuck — Financial Analysis

Search Companies

search_companies

Read-only

Use this when you have a company name or an ambiguous ticker and need the exact ticker (or CIK) before calling other tools. Fuzzy name/ticker match: handles partial names ("micro" -> MSFT), typos, and ticker variations. Returns ticker, full name, CIK, SIC, filer type (domestic / foreign private issuer / fund — i.e. which form family to expect), fiscal year-end, and the SEC EDGAR entity-page link (verify the match + see the full filing history) for each match.

Delisted / renamed / acquired companies are resolvable by current OR former name if they filed with the SEC in roughly the last five years (e.g. "American Software" → Logility, "Chase Manhattan" → JPM); older ones may not be found. They are returned ranked below active matches, flagged [delisted], with their CIK. They have no current ticker — pass the returned cik to downstream tools (company tools accept a CIK in place of a ticker, except get_stock_price, which needs a ticker).

Not for concept/theme/industry discovery ("gold miners", "LNG exposure", "companies mentioning tariffs") — it matches company names only, not what companies do. Use search_sec_filings (full text of filings) or screen_companies (metric + sector filters).

Coverage boundary: MetricDuck is SEC-EDGAR only, and this tool is its coverage check. A no-match on a non-US local-exchange symbol (e.g. 3087.T, LSE:HSBA, 7203:JP) is a coverage boundary, not a lookup miss — the tool says so explicitly and you should treat it as terminal (don't retry ticker variations). Foreign issuers that file a US 20-F/40-F ARE covered (see query).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum results (default 5, max 20)
`query`	Yes	Company name or ticker (supports partial matches and typos). 2-5 uppercase letters are read as a ticker: pass an all-caps NAME that is not a ticker ("AMCOR") in normal casing ("Amcor"). A miss returns near-matches when possible. Foreign issuers filing a US 20-F/40-F (HSBC, Toyota, Novo Nordisk): use the company name, not a local symbol.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations cover readOnly/destructive/openWorld, so the bar is lower. The description adds meaningful context: fuzzy matching handles partial names and typos, delisted companies are ranked lower and flagged [delisted], and the terminal no-match semantics for non-US symbols. Doesn't describe return ordering details or response shape, but that's minor.

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?

Front-loaded with the primary use case, then bolded sections for delisted handling, not-for cases, and coverage boundaries. Slightly long, but each section earns its place given the tool's role as a routing/coverage check.

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?

Given the tool's pivotal role as a resolver and coverage check, the description is complete: it explains what it returns, how delisted entities behave, what it's not for (with alternatives), and the terminal no-match behavior. No output schema exist, and the description compensates by enumerating returned fields.

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%, so baseline is 3. The description adds non-obvious operational guidance beyond the schema: the 2-5 uppercase letters ticker heuristic, the tip to pass all-caps names in normal casing, and the foreign issuer name-vs-local-symbol rule. This compensates for the subtle pitfalls the raw schema might not convey.

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?

States a specific verb+resource (resolve company name/ticker to canonical ticker or CIK) and explicitly scopes the tool as a prerequisite step before other tools. Clearly distinguishes itself from search_sec_filings and screen_companies by naming them as alternatives for different use cases.

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?

Explicit when-to-use (need exact ticker/CIK from a name or ambiguous ticker), when-not-to-use (concept/theme/industry discovery, with named alternative tools), and a critical routing rule for delisted companies (pass returned cik downstream, except get_stock_price). Also warns that a no-match on a non-US symbol is terminal.

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

All MetricDuck — Financial Analysis tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?