Skip to main content
Glama

lianban-a-share-review

get_emotion_mainlines

SVIP 专享:获取最近 30 个交易日的情绪温度、阶段和市场主线,最新日期在前。引用请署名“连板网”并附对应页面链接。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_emotion_mainlines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does disclose several real traits: an SVIP access requirement, a fixed 30-trading-day window (no user-controlled range), and newest-first ordering. It says nothing about the shape or semantics of the returned sentiment values, and there is no output schema to fill that gap.

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?

A single dense sentence with the access tier and data scope front-loaded, followed by the ordering guarantee and the attribution obligation. No filler, and the most decision-relevant facts (SVIP restriction, 30-day window) come first.

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?

For a zero-parameter read tool with no output schema, the description covers access tier, time window, ordering, and a citation obligation. The remaining gap is that the meaning of the returned 'emotion temperature' and 'stage' values is never characterized, which an agent would need to interpret results.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the fixed 30-day window is correctly presented as baked-in behavior rather than a configurable input. Baseline 4 applies for a parameterless tool.

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: retrieves sentiment temperature, stage, and market mainlines for the last 30 trading days, newest first. The scope and ordering make the result predictable, but the description never names or contrasts with siblings like get_daily_review or get_lhb, so an agent must infer the split from names alone.

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?

'SVIP 专享' signals a paid-tier prerequisite, which implicitly tells the agent when the call is permissible. However, there is no explicit guidance on when to prefer this over get_daily_review or other sibling endpoints, leaving the selection decision to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources