Skip to main content
Glama
Sign In
hyperdrive-mesh

hyperdrive-mesh

by tastenkasperle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

p2p_drive_connect

Connect to an existing remote Hyperdrive by supplying its 64-character hexadecimal public key over DHT.

Instructions

Verbindet sich mit einem bestehenden Remote-Hyperdrive über dessen 64-stelligen hexadezimalen Public Key via DHT.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "p2p_drive_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesDer 64-stellige Hex-Public-Key des Remote-Drives.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses the DHT mechanism and that the target drive must already exist, but says nothing about what a successful connection yields, whether it joins a swarm, idempotency, or failure behavior for an unreachable key.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tightly packed sentence with the action front-loaded and no redundant filler. Everything present earns its place, though the very terse phrasing leaves behavioral gaps that brevity alone does not justify.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, no-output-schema tool this is close to adequate, but the absence of annotations means the description should have covered at least the connection outcome and error conditions. As written, an agent knows what to pass but not what to expect back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the single parameter is already fully documented in the schema. The description restates the same 64-char hex key format without adding syntax, encoding, or sourcing guidance beyond it, which matches the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (connects) plus resource (an existing remote Hyperdrive) and even the mechanism (via DHT and a 64-char hex public key). This implicitly separates it from p2p_drive_create (which makes a new drive), though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'bestehenden' (existing) implies the tool is for joining a drive that already exists rather than creating one, giving implied usage context. However, there is no explicit when-to-use, when-not-to-use, or reference to alternative siblings such as p2p_drive_create or p2p_swarm_status.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools