Skip to main content
Glama

Finnhub (Unofficial)

Finnhub Search Symbol

finnhub_search_symbol
Read-onlyIdempotent

Search for stock ticker symbols by company name or keyword. Returns matching symbols with descriptions. Example: search_symbol({ query: "apple" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "apple"
    },
    "name": "finnhub_search_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query, company name or keyword, e.g. "apple", "tesla"
_apiKeyYesFinnhub API key

Output Schema

NameRequiredDescriptionDefault
countYesNumber of matching results
resultsYesList of matching symbols

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search query — company name or keyword, e.g. \"apple\", \"tesla\""New value: +"Search query, company name or keyword, e.g. \"apple\", \"tesla\""
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only that results include symbol plus description; it says nothing about fuzzy matching, result caps, ranking, or behavior on empty/ambiguous queries — relevant for an open-world search.

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?

Two short sentences plus an example, with the core action front-loaded and no filler. The inline example slightly duplicates the schema's 'examples' array but costs little.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile; the description only needs to establish action and input intent, which it does. It is thin on search behavior (matching rules, result limits), which keeps it short of a 5.

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?

Schema description coverage is 100%, so the baseline is 3. The description restates that query is a company name or keyword, which duplicates the schema rather than adding format or matching semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Search for stock ticker symbols by company name or keyword,' plus what comes back ('matching symbols with descriptions'). It does not differentiate from ambiguous siblings such as company_register_search, but the resource is unmistakable.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no named alternative for looking up a company when the ticker is already known or when a different company tool is more appropriate. The example call implies basic usage but gives no selection criteria.

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.