daily-brief
Aggregated daily brief combining phase_signal + ji_sensing + indices.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Zhiji Daily Report — Market Brief
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not disclose behavioral traits such as refresh rate, caching, output format, or any side effects.
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?
Single sentence with all essential information; no filler or redundancy.
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?
Given low complexity and absence of annotations/output schema, the description is too sparse. It does not specify output shape, usage conditions, or how it integrates with sibling tools.
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?
Tool has zero parameters, so baseline is 4. Description adds context about combining sources, which goes beyond the empty schema.
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?
Description clearly states verb ('combining') and resource ('daily brief'), and explicitly names the three sources, distinguishing it from sibling tools that cover individual signals.
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 aggregated brief versus the individual signal tools. Lacks any context or alternatives.
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.