Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance company profile

yahoo_finance_profile_get
Read-onlyIdempotent

Fetch a company's Yahoo Finance profile by ticker symbol, including address, officers, sector, and industry to support fundamental research.

Instructions

Get Yahoo Finance company profile, address, officers, sector and industry. Requires symbol.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesRequired. Ticker symbol, case-insensitive, e.g. `AAPL`, `^GSPC`, `EURUSD=X`, `BTC-USD`, `7203.T`.
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

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 and idempotency profile is covered structurally. The description adds nothing beyond that — no mention of data freshness, upstream rate limits, partial-data behavior for symbols lacking officer or address data, or response shape. With annotations carrying the safety story, the description still leaves behavioral gaps unaddressed.

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 no filler, and the field enumeration is front-loaded ahead of the requirement note. It is efficient, though the trailing "Requires `symbol`" clause is redundant with the schema and earns little space.

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-only lookup with no output schema, the description gives an adequate sketch of returned fields but omits how this differs from the many overlapping profile-adjacent siblings and says nothing about coverage or failure modes for obscure tickers. Minimum viable rather than complete.

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 all four parameters (including the ticker pattern and the context/llm_model/conversation_id instructions) are documented in the schema itself. The description's "Requires `symbol`" merely repeats a required-field fact already present. Baseline 3 applies because the schema does the heavy lifting and the description adds no new parameter meaning.

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 and resource ("Get Yahoo Finance company profile") and enumerates the content returned: address, officers, sector and industry. It does not distinguish this tool from siblings such as yahoo_finance_sector_get, yahoo_finance_industry_get, or yahoo_finance_statistics_get, which overlap on the same fields, so an agent cannot fully rule out alternatives from the text 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 usage statement is "Requires `symbol`", which is a prerequisite already enforced by the schema's required list. There is no guidance on when to choose this profile tool over the sector, industry, statistics, or instrument siblings, and no exclusions or context conditions.

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