Skip to main content
Glama

Stock Expert AI Research

Stock Expert AI: find a ticker

stockexpertai_search_ticker
Read-onlyIdempotent

Resolve a company name (or a partial ticker) to US ticker symbols covered by Stock Expert AI. Use before other tools when the user names a company rather than a symbol ("Nvidia", "Micron", "Berkshire"). Args: query (string, 1-80 chars); limit (int 1-10, default 5). Returns (structuredContent): { query, matches: [{ ticker, company, exchange, canonicalUrl }] }. Errors: empty matches — the company may not be US-listed or the name may need to be more specific. Derived output only: Stock Expert AI's own ratings, sentences and dates. Raw market figures (price, market cap, P/E, EPS, revenue) are not returned — full figures on the page (canonicalUrl).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "stockexpertai_search_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesCompany name or partial ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the bar is lower, yet the description still adds real context: the structuredContent shape, the empty-matches error condition and its likely causes (non-US listing, name too generic), and the important limitation that only Stock Expert AI's derived ratings/text are returned, with raw market figures available solely on canonicalUrl. That last point prevents a downstream agent from expecting price or P/E data.

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 purpose and routing rule, then cleanly segmented into Args / Returns / Errors / caveat lines, which is easy to scan. A few tokens are spent echoing schema constraints (1-80 chars, 1-10, default 5) that the schema already encodes.

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?

No output schema exists, and the description supplies the return shape, the error case, and a data-availability caveat — enough for an agent to call it and interpret the result correctly. Nothing material is missing for a two-parameter lookup.

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 only 50% (query documented, limit not), and the description fills that gap with "limit (int 1-10, default 5)" plus the query range. However, it largely restates the machine-readable min/max/default rather than explaining what limit controls (the cap on returned matches), so it compensates without fully adding meaning.

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?

"Resolve a company name (or a partial ticker) to US ticker symbols covered by Stock Expert AI" names a specific verb and resource plus a coverage scope. Sibling tools (summary, compare, earnings, screen) all operate on symbols, so this resolver is clearly the entry point that produces those symbols.

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?

"Use before other tools when the user names a company rather than a symbol" gives both a sequencing rule and the condition that selects this tool, with concrete name examples ("Nvidia", "Micron", "Berkshire"). The complementary case — user supplies a symbol, so call a sibling instead — is implied and effectively covered by the same sentence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources