Accept Terms of Service. Required before any paid tool executes. FREE.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your Hedera account ID / API key (e.g. 0.0.456789) | |
| confirmed | Yes | Must be true. Passing false is a no-op. | |
| terms_version | Yes | The terms version you are accepting — must match the current version returned by get_terms. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false and destructiveHint=true, so the description doesn't need to restate mutability. It adds that the operation is FREE and a prerequisite, but doesn't elaborate on what 'destructive' means or side effects of acceptance; with destructiveHint true, more clarification would be valuable.
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?
Two short sentences, front-loaded with the core action. 'FREE' is perhaps extraneous but conveys cost context; overall very concise with no waste.
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 simple prerequisite tool, the description plus rich schema is nearly complete. It covers when to use, required parameters, and validation rules. Missing only return values/no-op behavior, but those are minor for this tool.
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?
Schema covers 100% of parameters with detailed descriptions (api_key format, confirmed must be true, terms_version must match get_terms). Description adds no parameter-level detail beyond the schema, so baseline 3 applies.
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?
Description uses specific verb 'Accept' with direct object 'Terms of Service', clearly identifying the tool's function. It also adds differentiating context ('Required before any paid tool executes') that distinguishes it from sibling tools like get_terms.
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?
Explicitly states the tool is required before any paid tool executes, giving clear invocation context. It doesn't name alternatives or exclusions, but the prerequisite framing is strong enough; get_terms is referenced indirectly via schema for version.
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.