Skip to main content
Glama

search_events_by_stock

Read-onlyIdempotent

Query A-share stock events by stock code(s) to monitor portfolios or watchlists. Returns structured events for share reduction, delisting risk, regulatory letters, lockup expiration, and share buyback.

Instructions

Query structured A-share announcement events by stock code(s). Returns events for: share_reduction (减持), delisting_risk (ST/退市), regulatory_letter (监管函/问询函), lockup_expiration (限售解禁), share_buyback (回购). Each event includes: event_id, event_type, stock_code, stock_name, ai_summary, confidence_tier, structured_payload, and announcement_date. Use when: you know the stock code(s) and want to check recent events for those stocks. Use this for portfolio monitoring, watchlist scanning, or single-stock deep dives. Do NOT use when: you want to search by event type across all stocks (use search_events_by_type), or when you need a specific shareholder's events (use search_events_by_shareholder). Supports cursor-based pagination — use the cursor field in the response to fetch the next page. Returns: {data: [...], cursor: <next_cursor_or_null>, has_more: bool}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stock_codesYesComma-separated 6-digit stock codes. Example: '002272,600519,300750'.
statusNoFilter by event status. Options: active, updating, closed, corrected, archived. Empty = active + updating.
confidence_tierNoFilter by confidence tier. Options: verified, likely, uncertain. Empty = all.
cursorNoPagination cursor from previous response. Leave empty for first page.
limitNoMax results per page. Default: 20, Max: 200.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety. The description adds value by explaining cursor-based pagination and the response structure, which are beyond the annotations.

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 a single, well-organized paragraph that front-loads the purpose, lists event types, provides usage guidance, and explains pagination. It is concise without unnecessary words.

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?

Given no output schema, the description fully describes the return fields (event_id, event_type, etc.) and pagination response format. It covers all 5 parameters implicitly and provides sufficient context for usage.

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 coverage is 100% with good descriptions. The description adds minor value such as an example for stock_codes and explanation of cursor usage, but does not significantly augment the schema.

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 states 'Query structured A-share announcement events by stock code(s)' and lists specific event types (share_reduction, delisting_risk, etc.), distinguishing it from siblings like search_events_by_type and search_events_by_shareholder.

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

Usage Guidelines5/5

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

Explicitly states when to use ('when you know the stock code(s)') and when not to, providing two named alternatives (search_events_by_type, search_events_by_shareholder). This helps the agent choose correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NengjiangLunpi/astockevent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server