Skip to main content
Glama
Sign In
akshare-one-mcp

akshare-one-mcp

by zwldarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get News Data

get_news_data

Fetch stock-related news for a specified symbol from Eastmoney or THS, falling back to the other source if needed and returning a set number of recent records.

Instructions

Get stock-related news data.

With fallback on, the sources are tried as 'eastmoney' and 'ths', starting with the requested one.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_news_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoData sourceeastmoney
symbolYesStock symbol/ticker (e.g. '000001')
fallbackNoTry the domain's other data sources when this one fails or has no data
recent_nNoNumber of most recent records to return

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / fallback
      Added value: +{
+  "default": true,
+  "description": "Try the domain's other data sources when this one fails or has no data",
+  "type": "boolean"
+}
    • addedInput schema / properties / source
      Added value: +{
+  "default": "eastmoney",
+  "description": "Data source",
+  "enum": [
+    "eastmoney",
+    "ths"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed4 schema fields changedv1.0.0
    • removedInput schema / properties / recent_n / title
      Removed value: -"Recent N"
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses fallback ordering—trying the requested source first, then the other source—but it does not describe permissions, rate limits, failure behavior beyond fallback, or other operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no waste. The core purpose is front-loaded, followed by the key fallback behavior.

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?

The tool has a full input schema, an output schema, and clear parameter documentation. The description supplies the important fallback sequencing, and return values need not be explained because an output schema exists, though additional usage context would make it stronger.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3. The description adds meaning to the fallback parameter by specifying that sources are tried as 'eastmoney' and 'ths' starting with the requested one, which clarifies behavior beyond the schema's generic fallback text.

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 stock-related news data.' This clearly separates it from sibling tools that handle financial statements, historical data, or realtime data, though it does not explicitly name those alternatives.

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?

Usage is implied by 'stock-related news data,' so an agent can infer it should call this for news rather than financial metrics or price history. However, there is no explicit guidance on when not to use it or how it compares with any alternative news-related tool.

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