phase-signal
A-share HS300 phase transition signal (Phi, D, chi, delta_F, SoTI, state). Real-time Landau-Ginzburg framework analysis.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Zhiji Daily Report — Market Brief
TDQS
B3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavioral traits. It mentions 'real-time' but does not specify whether the tool is read-only, requires authentication, has limits, or any side effects. The behavioral information is insufficient.
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?
Single sentence, front-loaded with key terms. It is concise but could be slightly more structured (e.g., separating the list of signals). Meets conciseness standard.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description must explain return values. It lists indicator names but does not describe their types, ranges, or formats. This leaves the agent uncertain about what to expect.
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?
No parameters, so schema coverage is trivially 100%. The description does not need to add parameter details. Baseline 4 is appropriate.
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?
Description states it provides a 'phase transition signal' for A-share HS300, listing specific indicators and mentioning the analysis framework. The verb is implicit but the resource is clear. It does not explicitly distinguish from siblings like 'arena-signal', but the specific indicators give some differentiation.
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?
No guidance on when to use this tool over alternatives or any context about prerequisites. The description only states what it does, not when it should be invoked.
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.
TDQS
B3.3/5.0
Disambiguation3/5
Some overlap exists: daily-brief and signal-latest both aggregate multiple signals, and arena-signal and phase-signal both provide phase signals for different markets. Descriptions help distinguish but ambiguity remains.
Naming Consistency3/5
Names use hyphens but vary in structure: some are compound nouns (e.g., arena-signal, phase-signal), others are more descriptive (daily-brief, signal-latest). No strong consistent pattern.
Tool Count4/5
With 5 tools, the count is reasonable for a market brief server. However, the presence of two aggregate endpoints suggests slight redundancy, but not overly heavy.
Completeness4/5
The set covers global market signals, A-share analysis, and aggregated briefs. Missing historical data or detailed comparisons, but core daily briefing needs are met.