Loading ToolBench
Hive MCP server implementing the EIP-712 over USB/DMK ledger-bridge integration spec (shisa-ai/shisad contrib/ledger-bridge)
Server implements 5 domain-specific tools for Ledger/EIP-712 integration with complete input schemas and descriptions. Naming follows verb_noun pattern (create, verify, query, attest). Descriptions are substantive (100-200 chars) and explain WHAT, WHEN, and domain context. However, output schemas are not documented, LLMs cannot predict response structure. Parameter descriptions are good but lack format constraints (e.g., 'intent_id' should specify UUID format). No error handling guidance or recovery paths. Tool composition is sound (single responsibility), but missing pagination/limits for directory tool.
Return the required ConfirmationLevel for an intent based on action type and optional amount. Returns the integer level (0–4) and its name from the ConfirmationLevel enum (SOFTWARE=0, REAUTHENTICATED=1, BOUND_APPROVAL=2, SIGNED_AUTHORIZATION=3, TRUSTED_DISPLAY_AUTHORIZATION=4).
Build an IntentEnvelope with EIP-712 domain separator and intent_envelope_hash for Ledger device signing. Implements the signer-backend contract from shisa-ai/shisad contrib/ledger-bridge.
Verify that a supplied intent_envelope_hash matches the canonical hash of an IntentEnvelope body. Returns match=true|false and the recomputed hash.
Return the Hive ledger-bridge partner integration directory: shisa-ai/shisad reference, Ledger Live partner program link, and brand-attributed Hive contact.
Hive-side attestation that an intent_envelope_hash has reached SIGNED_AUTHORIZATION (level 3) or TRUSTED_DISPLAY_AUTHORIZATION (level 4). Stores the attestation record against the agent DID. Does not perform on-chain settlement — attestation only.
Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting). Tools return objects but no schema is visible in code or descriptions.
Parameter format constraints missing. 'intent_id' should specify UUID format; 'agent_did' should specify W3C DID format; 'ecdsa_signature' should specify hex encoding. Descriptions state these informally but lack JSON Schema pattern or format declarations.
No error handling guidance. Tools do not document failure modes (e.g., invalid chain_id, signature verification failure, DID not found). LLMs receive raw errors with no recovery path.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
ledger_partner_directory has no input parameters but description does not explain what it returns or when to call it. Appears to be a static reference tool but lacks discovery context.
No idempotency guarantees documented. ledger_signed_authorization_attest is a WRITE operation, should state whether repeated calls with same hash/DID create duplicates or are idempotent.