Skip to main content
Glama
yfinance-ai MCP server

yfinance-ai MCP server

by lkcair

get_company_officers

Read-onlyIdempotent

Retrieve company officers and key management for a stock ticker, including their titles and compensation, using Yahoo Finance data.

Instructions

Get company officers and key management.

Args: ticker: Stock ticker symbol

Returns: List of company officers with titles and compensation

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": {
      "ticker": "<ticker>"
    },
    "name": "get_company_officers"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 without the description's help. The description adds the content of the payload (titles and compensation), which is mildly useful context, but says nothing about coverage, freshness, or remote-fetch behavior implied by openWorldHint.

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?

Front-loaded purpose followed by a compact Args/Returns block with no filler. The 'Returns' section is arguably redundant given an output schema exists, but it is not harmful and the whole thing stays short.

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?

With an output schema present, the description need not detail return values, so leaving that incomplete is acceptable; it covers it briefly anyway. What is missing is routing guidance in a context with dozens of similar get_* tools, which is the main gap an agent would hit when choosing this tool.

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 0%, so the description carries the burden, and it does label the single parameter as 'Stock ticker symbol'. However that is little more than restating the parameter name; it gives no format, exchange-qualification, or case-sensitivity guidance. Minimum viable for a one-parameter tool.

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 company officers and key management') in the first line, which is enough to distinguish it from sibling tools like get_company_info or get_major_holders at a glance. It does not explicitly name which sibling covers adjacent data (insider roster, major holders), so differentiation is inferred rather than stated.

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 when-to-use guidance, no exclusions, and no mention of alternatives among the ~60 sibling financial tools. The agent must infer from the name alone when officers data is the right pick versus get_insider_roster_holders or get_company_overview.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.