Skip to main content
Glama
Johnhyeon

StockLens

by Johnhyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_us_news

Read-onlyIdempotent

Get US stock news headlines for a ticker. Filter out unrelated Yahoo articles using relevance flags or direct_only for stories centered on that stock.

Instructions

US stock news — 미국 주식 관련 뉴스 헤드라인 (관련도 판정 포함). "AAPL 뉴스", "Tesla news", "NVDA headlines" 같은 질문에 사용합니다.

Yahoo 피드에는 다른 종목이 중심인 기사가 섞여 옵니다(실측: AAPL 피드에 InterDigital·NVDA 단독 기사). 기사마다 관련도(direct/comparison/ supply_chain/list_or_etf/mention/unrelated)와 근거가 붙습니다. 이 종목이 주제인 기사만 원하면 direct_only=True.

Args: ticker: US 티커 limit: 헤드라인 개수 (기본 10) direct_only: True 면 이 종목이 주제(direct)인 기사만 남깁니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
tickerYes
direct_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.3
    • removedInput schema / properties / direct_only / default
      Removed value: -false
    • removedInput schema / properties / limit / default
      Removed value: -10
  2. Changed1 schema field changedv1.0.1
    • addedInput schema / properties / direct_only
      Added value: +{
+  "default": false,
+  "title": "Direct Only",
+  "type": "boolean"
+}
  3. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses a real behavioral quirk: Yahoo feeds include unrelated articles, and each result is tagged with a relevance category. It also explains the direct_only filtering option, providing useful operational context beyond what annotations reveal.

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?

The description is organized with a purpose statement, rationale, and an Args list, making it easy to scan. Minor redundancy exists because direct_only is explained both in the prose and again in the Args section, but the overall length is justified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read-only tool with an output schema, the description covers what the tool does, when to use it, the data-source caveat, and every parameter. Nothing an agent needs to select or call it correctly is missing.

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

Parameters5/5

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

The schema has 0% description coverage, but the description fully documents all three parameters: ticker, limit (with default 10), and direct_only (with clear semantics). This completely compensates for the empty schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the operation as fetching US stock news headlines and adds the distinctive relevance-classification feature. The example queries make the tool's purpose immediately recognizable, and it is distinct from broader sibling tools by the 'US stock' scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete query examples ('AAPL news', 'Tesla news', 'NVDA headlines') and explains when to set direct_only, so an agent knows when to invoke it. It does not explicitly mention alternatives or exclusions such as when to prefer get_news, so it stops short of full routing guidance.

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