Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance industry

yahoo_finance_industry_get
Read-onlyIdempotent

Retrieve Yahoo Finance performance data for a specified industry, including top and growing companies, to support market research and investment analysis.

Instructions

Get Yahoo Finance industry performance and top and growing companies. Requires industry.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
industryYesRequired. Industry key such as `software-infrastructure`, 1 to 80 characters; case-insensitive, spaces or underscores become hyphens.
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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the returned subject matter (performance plus top and growing companies), but says nothing about whether an unknown industry key errors or returns empty, or about any freshness/caching of quotes.

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 with the data scope front-loaded and the requirement second; nothing is wasted. It is borderline terse for a tool with three required parameters and no output schema, but no sentence is filler.

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 tool with full schema coverage and annotations, the core need is met, and the description sketches the return contents in the absence of an output schema. However, it omits the return shape (e.g. performance metrics vs. company lists) and never mentions the conversation_id sequencing constraint, which matters because the schema forbids parallel calls before the ID is obtained.

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%, including the normalization rules (case-insensitive, spaces/underscores to hyphens) and the meaning of `context`, `llm_model` and `conversation_id`. The description adds no parameter meaning beyond repeating that `industry` is required, 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?

States a specific verb and resource ('Get Yahoo Finance industry performance and top and growing companies'), and the content scope tells the agent what data comes back. It does not distinguish itself from the very similar sibling `yahoo_finance_sector_get`, so the industry-vs-sector boundary is left to inference.

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?

The only usage statement is 'Requires `industry`', which is a prerequisite restated from the schema rather than a when-to-use rule. There is no guidance on when to pick this over sector, instrument, or screener tools, and no note on what to do when an industry key is invalid.

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