Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance sector

yahoo_finance_sector_get
Read-onlyIdempotent

Retrieve Yahoo Finance performance data, top companies, and industries for a specified sector to analyze market trends and compare sector constituents.

Instructions

Get Yahoo Finance sector performance, top companies and industries. Requires sector.

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

Input Schema

NameRequiredDescriptionDefault
sectorYesRequired. Sector key such as `technology`, 1 to 80 characters; case-insensitive, spaces or underscores become hyphens.
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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds that the response covers sector performance plus top companies and industries, which is genuine return-content information given there is no output schema. It discloses nothing about auth needs, rate limits, or data freshness, so it goes only slightly beyond the annotations.

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 stated immediately after. Nothing is wasted, though the second sentence duplicates the schema's required-field declaration instead of earning its place with new information.

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 read-only lookup with no output schema, the description at least names the three payload areas an agent can expect. However, it omits the response shape, how sector keys are discovered, and any differentiation from the many sibling `*_get` tools, leaving real gaps for a tool in a 30+ member family.

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 schema already documents the sector key format (1–80 chars, case-insensitive, spaces/underscores normalized to hyphens) and the context/llm_model/conversation_id conventions in detail. The description's "Requires `sector`" is a restatement of the schema with no added meaning. Baseline 3 applies when the schema carries parameter 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?

The description uses a specific verb+resource ("Get Yahoo Finance sector performance, top companies and industries") and enumerates the returned data domains, so an agent knows this is the sector-level aggregation view rather than a single-instrument view. It does not explicitly name the closest sibling, yahoo_finance_industry_get, so the sector-vs-industry boundary must be inferred from the name alone.

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 guidance is "Requires `sector`," which restates the required field rather than explaining when to choose this tool. There is no mention of when to prefer yahoo_finance_industry_get for industry-level data, no prerequisites, and no note about which sectors are valid or where to obtain sector keys.

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