Skip to main content
Glama
InvestBrain

InvestBrain

tushare_get_stock_pledge_status

Retrieve pledge status and pledge ratio for a given Tushare stock code to assess shareholder pledge risk.

Instructions

Get stock pledge (股权质押) status (Tushare API: pledge_stat).

Args:
    ts_code: Tushare stock code (e.g., "600519.SH")

Returns:
    dict: Pledge ratio and status

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": {
      "ts_code": "<ts_code>"
    },
    "name": "tushare_get_stock_pledge_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
ts_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it only says it returns 'pledge ratio and status'. It does not state that this is a read-only lookup, whether auth/token is required, rate limits, or error behavior. The 'Returns' line adds minor value but is thin for a zero-annotation tool.

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 short and front-loaded with the core purpose, followed by Args/Returns sections that are easy to scan. The docstring-style framing is slightly heavier than needed for one parameter but nothing is wasted.

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?

For a one-parameter retrieval with no output schema and no annotations, the description covers the input format and names the return fields, which is minimally adequate. However, the return value description ('Pledge ratio and status') is vague, leaving the agent unsure of the actual dict structure.

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 description coverage is 0%, so the description must compensate for the single parameter—and it does by specifying 'Tushare stock code' with a concrete format example ('600519.SH'). This is meaningful detail absent from the bare string-typed schema.

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 pledge status') and names the backing Tushare endpoint (pledge_stat), so the agent knows exactly what data it retrieves. It does not explicitly differentiate itself from the other tushare_* data endpoints, but the resource is narrow enough to be unambiguous.

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?

There is no statement of when to use this tool versus siblings like tushare_get_valuation_multi or other fundamental endpoints, and no prerequisites or exclusions are given. The agent must infer usage from the name 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