hcs_understand
Analyze Hedera Consensus Service topics to detect anomalies, identify trends, extract entities, or assess risks using historical data patterns.
Instructions
Deep pattern analysis of an HCS topic - anomaly detection, trend analysis, entity extraction, or risk assessment. Costs 0.50 HBAR.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your HederaIntel API key | |
| analysis_type | Yes | Type of analysis to perform | |
| topic_id | No | Hedera topic ID. Defaults to the HederaIntel platform topic. | |
| lookback_days | No | Days of history to analyze (default 7, max 30) |
Implementation Reference
- src/modules/hcs/tools.js:91-104 (handler)The handler for hcs_understand that processes the topic messages using deepAnalyze.
if (name === "hcs_understand") { const payment = chargeForTool("hcs_understand", args.api_key); const topicId = args.topic_id || PLATFORM_TOPIC; const messages = await getTopicMessages(topicId, 100); const analysis = await deepAnalyze(messages, args.analysis_type); return { topic_id: topicId, analysis_type: args.analysis_type, messages_analyzed: messages.length, ...analysis, payment, timestamp: new Date().toISOString(), }; } - src/modules/hcs/tools.js:36-52 (schema)The MCP schema definition for hcs_understand tool.
name: "hcs_understand", description: "Deep pattern analysis of an HCS topic - anomaly detection, trend analysis, entity extraction, or risk assessment. Costs 1.0 HBAR.", inputSchema: { type: "object", properties: { topic_id: { type: "string", description: "Hedera topic ID. Defaults to the HederaIntel platform topic." }, analysis_type: { type: "string", enum: ["anomaly_detection", "trend_analysis", "entity_extraction", "risk_assessment"], description: "Type of analysis to perform", }, lookback_days: { type: "number", description: "Days of history to analyze (default 7, max 30)" }, api_key: { type: "string", description: "Your HederaIntel API key" }, }, required: ["analysis_type", "api_key"], }, },