Skip to main content
Glama
Sign In
fin-advisor

fin-advisor

by TTNAN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_company_news

Read-onlyIdempotent

Retrieve recent news headlines for a specified company ticker to support market research and event tracking. Use it to gather cached Yahoo Finance RSS headlines with a configurable limit.

Instructions

查询公司近期新闻标题（Yahoo Finance RSS 缓存）。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results come from a cached Yahoo Finance RSS feed, which hints at possible staleness. However, it says nothing about freshness windows, item ordering, or what happens when no news is found.

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?

A single short sentence, front-loaded with the resource and ending with the source. Nothing is wasted, though the brevity edges into under-specification rather than tightness.

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?

An output schema exists, so return-value explanation is not required, and annotations cover the safety profile. Still, with two undocumented parameters and no usage context, an agent lacks enough to pick sensible limits or know how this compares to sibling data tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden. It only implies that 'ticker' identifies the company; the 'limit' parameter (default 5) is never mentioned, and no format guidance (e.g., exchange suffix) is given for the ticker.

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 states a specific verb+resource: it retrieves recent company news headlines. It also names the data source (Yahoo Finance RSS cache). It does not explicitly contrast with siblings, but the resource is distinct enough that an agent can separate it from get_quote or search_filings.

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 guidance on when to use this tool versus search_filings or get_quote, and no prerequisites or exclusions are stated. The agent must infer from the name alone that this is for news, not for filings or prices.

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