Skip to main content
Glama
Sign In
deepq-financial-toolkit

deepq-financial-toolkit

by shenqingtech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

板块消息面：获取概念或行业板块指定日期段内的新闻消息

sectorNewsAnalysis

Analyze news coverage for specific industry sectors or concepts within defined date ranges to identify market trends and sentiment.

Instructions

板块消息面：获取概念或行业板块指定日期段内的新闻消息

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": {
      "query": "<query>"
    },
    "name": "sectorNewsAnalysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateNo结束时间，不填则默认为今天
maxCntNo最大返回条数，默认3条
queryYes概念或行业板块名称
startDateNo开始时间，不填则默认为今天

Output Schema

NameRequiredDescriptionDefault
msgYes
codeYes
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions '获取' (get) which implies a read operation, but doesn't disclose traits like rate limits, authentication needs, pagination, or what happens if no news is found. The description is minimal and lacks behavioral context beyond the basic operation.

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, efficient sentence that directly states the tool's function without waste. It is appropriately sized and front-loaded, making it easy to parse. However, it could be slightly more structured by separating purpose from context.

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?

Given the tool's moderate complexity (4 parameters, 1 required), no annotations, and the presence of an output schema (which handles return values), the description is minimally adequate. It covers the basic purpose but lacks behavioral details and usage guidelines. The output schema likely compensates for return value explanation, but the description should do more to address gaps in behavioral transparency.

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%, with all parameters well-documented in the input schema (e.g., 'query' as concept/industry sector name, date defaults). The description adds no additional meaning beyond the schema, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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

Purpose2/5

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

Tautological: description restates name/title.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention siblings such as 'etfRelatedNews' for ETF-related news or 'officialSecuNews' for official securities news, nor does it specify prerequisites or exclusions. Usage is implied by the description but not explicitly stated.

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