Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Yahoo Finance trending symbols

yahoo_finance_trending_list
Read-onlyIdempotent

Retrieves trending Yahoo Finance ticker symbols for a specified region, with an optional limit, so you can identify market movers for research or monitoring.

Instructions

List Yahoo Finance trending symbols for a region. Optional inputs: region and limit. Returns a list.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yahoo_finance_trending_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of trending symbols to return, 1 to 250. Default: 25.
regionNoMarket region, a two-letter code such as `US`, `GB` or `JP`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/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 almost nothing beyond that: 'Returns a list' is the only return information, and it says nothing about region defaults, rate limits, or freshness of the trending data. The sequencing constraint around conversation_id exists only in the schema, not here.

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?

Three short sentences with the core purpose front-loaded and no padding. The closing 'Returns a list' is nearly content-free and the 'Optional inputs' clause duplicates the schema, but neither harms readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with fully described parameters this is adequate, and the absence of an output schema is partly offset by 'Returns a list'. However, it never acknowledges the required context/llm_model metadata or the conversation_id dependency, leaving the agent to discover those solely from the schema.

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 region (two-letter code), limit (1-250, default 25) and the required context/llm_model fields are already fully documented. The description only repeats that region and limit are optional and adds no format or default detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource ('List Yahoo Finance trending symbols') scoped to a region, which is enough to distinguish it from same-named siblings like discord_games_trending_list. It never explicitly names or contrasts those alternatives, so it stops short of a 5.

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?

There is no guidance on when to use this versus yahoo_finance_screener_get, yahoo_finance_lookup, or yahoo_finance_quotes_list for symbol discovery, and no prerequisites or exclusions are stated. The only usage-adjacent content is that region and limit are optional, which is just restating the schema.

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

Deploy Server

Other Tools