Hedera contract deep analysis: activity, caller distribution, gas, risk, classification. 1.5 HBAR.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your HederaIntel API key | |
| contract_id | Yes | Hedera contract ID to analyze (e.g. 0.0.123456) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate a safe read-only operation (readOnlyHint=true, destructiveHint=false). The description adds the cost '1.5 HBAR' and the scope of analysis, which is useful beyond annotations, but does not disclose output format, latency, or other behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads the purpose and lists key features, including the cost, with no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex analysis tool without an output schema, the description covers the main purpose but omits return value details, prerequisites, or any additional context needed to fully understand the analysis output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% parameter description coverage, so the baseline is 3. The description does not add any parameter-specific meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool performs 'Hedera contract deep analysis' and enumerates specific aspects ('activity, caller distribution, gas, risk, classification'), making it distinct from sibling tools like contract_read or token_analyze.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage via 'deep analysis' and the listed analytical dimensions, but it provides no explicit when-to-use/when-not-to-use guidance or references to alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action (e.g., contract read vs. contract call vs. contract analyze; hcs monitor vs. hcs query vs. hcs understand). Even within closely related groups, descriptions clearly differentiate the specific purpose, so an agent is unlikely to select the wrong tool.
Most tools follow a domain_action pattern (e.g., contract_analyze, token_monitor, hcs_verify_record), but some are verb_noun (get_terms, confirm_terms) and a few are noun_noun (account_info, token_price, fixatum_score). While not perfectly uniform, the prefixes make the intended domain clear and the overall structure is readable.
With 25 tools, the server is on the heavy end of the typical MCP scope. While each tool serves a specific niche across multiple Hedera domains (contracts, HCS, tokens, identity, governance, Fixatum), the sheer number could increase selection complexity, but it remains within the borderline range rather than being excessive.
The server covers a broad range of read/analyze operations across major Hedera areas, plus essential write/verification capabilities (hcs_write_record, hcs_verify_record) and an onboarding flow (get_terms, confirm_terms). Minor gaps exist, such as no token transfer history or unregister/update for Fixatum, but the core analytical purpose is well covered.