Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Yahoo Finance screener fields

yahoo_finance_screener_fields_list
Read-onlyIdempotent

List available Yahoo Finance screener filter and output fields by instrument type so you can build accurate stock, ETF, crypto, or other screens; optionally include premium fields.

Instructions

List Yahoo Finance screener filter and output fields by instrument type. Optional inputs: instrumentType and includePremium. 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_screener_fields_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.
includePremiumNoInclude fields flagged premium. Default: false.
instrumentTypeNoInstrument type. Default: `equity`.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that output is scoped by instrument type and can include premium fields, which is useful context beyond annotations, but it says nothing about result size, rate limits, or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action and scope front-loaded, followed by the optional inputs. No filler or repetition.

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?

For a simple read-only listing tool with full schema coverage and no output schema, the description covers what is needed to call it. The only gap is a vague return statement ("Returns a list") that does not indicate the shape of the field entries, which matters somewhat since no output schema exists.

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 both meaningful parameters are already documented, including the default of equity and the default of false for premium. The description only restates that these inputs are optional, adding no new semantics such as what premium fields mean or how instrument type changes the field set.

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: list Yahoo Finance screener filter and output fields, scoped by instrument type. It is distinguishable from siblings like yahoo_finance_screeners_list or yahoo_finance_screener_get, though it never explicitly names those alternatives.

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 is given: nothing tells the agent to call this before constructing a screen, or how it differs from yahoo_finance_screeners_list or yahoo_finance_screener_search. The only hints are the optional parameter names, which do not amount to usage guidance.

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