Attach an existing k402 session key (from a previous open_session) so paid calls meter against its balance — use after reconnecting to the hosted endpoint, or to carry one funded session across clients. Returns the session's current balance. Free.
| Name | Required | Description | Default |
|---|---|---|---|
| session | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that it attaches a session key, returns current balance, and is free. No annotations present, so description carries full burden. Lacks details on idempotency or error cases but is fairly transparent.
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 front-loaded sentences, zero waste. Every sentence adds value without repetition.
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?
Covers purpose, usage context, return value, and cost. Lacks error conditions but is complete given the tool's simplicity.
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 has 0% description coverage, but the description explains that the single parameter is a session key from open_session, adding meaning beyond the schema type.
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 uses specific verb 'attach' and resource 'existing k402 session key', clearly stating the tool's purpose. It distinguishes from siblings like open_session (creates) and session_status (checks status).
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 tells when to use: after reconnecting or to carry session across clients. Provides context but does not explicitly mention when not to use or alternatives, though sibling tools imply alternatives.
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 has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. Even within related domains (e.g., covenant operations, proving steps), the functions are well-separated and described.
Most tools follow a verb_noun or noun_noun pattern with underscores, but there are some single-verb names like 'catalog' and 'classify'. Within subdomains naming is consistent (e.g., kaspa_*, covenant_*, prove_*). Minor deviations prevent a perfect score.
36 tools is on the high side for a typical MCP server, but the broad scope (blockchain, payments, ZK proving, text processing, search, registry) justifies the count. It borders on being too large for easy navigation but remains reasonable.
The server covers a wide range of functionalities with no critical gaps for its stated domain. Minor gaps exist (e.g., no direct Kaspa send transaction tool), but the covenant tools provide a workaround. Overall, the surface is fairly complete.