Skip to main content
Glama

首提流:此前 7 天没人提、刚被第一次提到的 A 股

get_first_mention_stocks
Read-onlyIdempotent

首提流:此前 7 天没人提、刚被第一次提到的 A 股。列出最近 N 小时内“首次被提到”的股票(此前 7 天一次都没被提过):首提时间、首提的 agency_id 和分数,以及首提之后到现在又被提了几次。适合发现新冒头的标的。(每次调用计费 1 次)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_first_mention_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNo回看小时数
limitNo返回条数,默认 100,最大 200
min_scoreNo只统计机构/大V分 ≥ 该值的提及(约 450~1500,1000 左右算中等;1050 约前 10%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / source
      Removed value: -{
      -  "default": "all",
      -  "description": "只看某类来源:community 社群/星球、forum 论坛/社区、web 网页、search 联网搜索、x X(推特)、news_report 新闻/研报;默认 all",
      -  "enum": [
      -    "all",
      -    "community",
      -    "forum",
      -    "web",
      -    "search",
      -    "x",
      -    "news_report"
      -  ],
      -  "type": "string"
      -}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent, closed-world profile, so the description's marginal value is the per-call billing note ('每次调用计费 1 次'), which is genuinely operationally useful and not in the structured data. It also specifies the semantics of the 'first mention' window, though it omits sort order and empty-result behavior.

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 definition is front-loaded with the concept before the return fields and the billing note, and it is short. The opening clause duplicates the title verbatim ('首提流:此前 7 天没人提、刚被第一次提到的 A 股'), which is a small amount of wasted space.

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

Completeness4/5

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

There is no output schema, so the description must — and does — enumerate what comes back: first-mention time, agency_id, score, and repeat-mention count. Combined with the billing disclosure, this is nearly sufficient; only result ordering and the interaction between the N-hour window and the fixed 7-day lookback remain unstated.

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%, and the schema's min_score description is unusually rich (450–1500 range, 1050 ≈ top 10%), so the burden is already carried. The description restates the N-hour window and the score field but adds no new parameter-level meaning beyond the schema, so the baseline 3 applies.

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 defines a specific, novel retrieval concept — stocks mentioned for the first time in the last N hours with no mentions in the preceding 7 days — and enumerates the returned fields (first-mention time, agency_id, score, subsequent mention count). This is clearly distinguishable from siblings like get_market_hot_stocks or get_accelerating_hot_stocks, which rank by heat rather than first appearance.

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

Usage Guidelines3/5

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

The phrase '适合发现新冒头的标的' gives a use case, so the intent is inferable, but there is no explicit when-to-use vs. when-not or any routing to alternative siblings such as get_accelerating_hot_stocks. The agent must infer the choice from the concept definition alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources