Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance market view

yahoo_finance_market_get
Read-onlyIdempotent

Retrieve Yahoo Finance market summaries, trading clocks, ticker lists, and currency data by region and language for financial research and monitoring.

Instructions

Get Yahoo Finance market summary, clock, ticker lists and currencies. Optional inputs: region and language.

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_market_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
languageNoLanguage tag for names and news, e.g. `en-US` or `ja-JP`.
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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds essentially nothing behavioral beyond that – no mention of latency, rate limits, freshness of quotes, or the fact that the required `context`/`llm_model` plumbing and the `conversation_id` handshake exist, which materially affects how the tool is invoked.

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, purpose front-loaded, no filler or repetition. It is efficient, though the brevity borders on under-specification rather than being genuinely tight prose.

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 market-overview tool with no output schema this is only just adequate: it tells the agent what categories of data come back but not their shape or relative cost. The heavier invocation requirements (context, llm_model, conversation_id sequencing) are covered by schema descriptions, which keeps this from being a larger gap.

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 every parameter is already documented in the schema, including the region pattern and language tag format. The description merely restates that `region` and `language` are optional, adding no semantics beyond the structured fields, so the baseline of 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 names a specific verb ('Get') and enumerates the concrete payloads: market summary, clock, ticker lists and currencies. That is more informative than a tautology, but it does not distinguish this broad market-overview tool from siblings such as yahoo_finance_quotes_list or yahoo_finance_trending_list, which plausibly overlap with 'ticker lists'.

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 statement of when to reach for this tool versus the many sibling finance endpoints; the only guidance is that `region` and `language` are optional. An agent must infer from the name alone that this is the general market-wide entry point rather than a per-instrument call.

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