Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Yahoo Finance predefined screeners

yahoo_finance_screeners_list
Read-onlyIdempotent

Lists Yahoo Finance predefined stock screeners with titles, helping you identify and choose screening categories before requesting specific results.

Instructions

List Yahoo Finance predefined screeners and their titles. 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_screeners_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered by structured data. The description adds only that titles are included in the response, a marginal return-value detail; it says nothing about what identifiers come back, ordering, or whether results are cached.

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, front-loaded sentences with no filler. The second sentence ('Returns a list.') is largely redundant with 'List ... ' and with the lack of an output schema, so it does not fully earn its place.

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 list endpoint with rich annotations this is close to sufficient, but it omits the one thing an agent needs to chain calls: whether screener keys/IDs (usable with yahoo_finance_screener_get) are returned alongside titles. No output schema exists to answer that question elsewhere.

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% and the three parameters (context, llm_model, conversation_id) are fully self-documented infrastructure fields with no domain arguments. The description adds no parameter meaning, which is acceptable at this coverage level but earns no bonus.

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 (List) and resource (Yahoo Finance predefined screeners) plus the returned attribute (titles), so the agent can distinguish it from data-oriented siblings like yahoo_finance_screener_search or yahoo_finance_screener_get. It stops short of naming which sibling to use for actual screening results.

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 guidance, no prerequisites, and no routing to alternatives such as yahoo_finance_screener_search or yahoo_finance_screener_get. Usage must be inferred entirely from the tool name and the word 'predefined'.

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