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

deepq-financial-toolkit

by shenqingtech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

基金底层资产：穿透分析基金底层重仓行业、重仓股票、重仓债券

fundUnderAssets

Analyze underlying holdings of funds including major industries, stocks, and bonds to understand portfolio composition and risk exposure.

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": "fundUnderAssets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes基金代码或基金名称

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.6/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. It mentions '穿透分析' (penetrating analysis) but doesn't disclose behavioral traits like whether it's read-only, requires authentication, has rate limits, or what the output format is. The description is too vague to inform the agent about how the tool behaves beyond its basic purpose.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for the agent to parse quickly.

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 that there's an output schema (which handles return values) and the input schema has full coverage, the description's job is reduced. However, for a tool with no annotations and potential complexity in analysis, the description could better explain scope (e.g., depth of analysis, data recency) or limitations. It's minimally adequate but lacks context about behavioral aspects.

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?

The input schema has 100% description coverage for the single parameter 'query', which is documented as '基金代码或基金名称' (fund code or fund name). The description doesn't add any meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 prerequisites, context, or compare with sibling tools such as 'etfUnderAssets' (for ETFs) or 'fundBasicInfo' (for general fund info). The agent must infer usage based on the name and description alone.

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