signal-latest
Complete signal payload including phase_signal + ji_sensing + indices. Single-call convenience endpoint.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Zhiji Daily Report — Market Brief
TDQS
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits; it states the output is a combined payload but lacks details on read-only nature or error handling.
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?
Two sentences efficiently convey the tool's purpose and value with no redundant information.
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?
The description covers the key output components but omits details of the payload structure; however, given no output schema, this is adequate for a simple aggregation endpoint.
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 input schema is empty with no parameters, so the description need not add parameter semantics beyond the schema, meeting the baseline for zero-parameter tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a complete signal payload combining phase_signal, ji_sensing, and indices, distinguishing it from sibling tools like phase-signal and ji-sensing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'single-call convenience endpoint' implies use when all three signals are needed, and sibling tool names provide clear alternatives for individual signals.
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.