Skip to main content
Glama
Sign In
hyperdrive-mesh

hyperdrive-mesh

by tastenkasperle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

p2p_drive_list

List all files and directories in a P2P Hyperdrive by supplying its hex key and optional directory prefix.

Instructions

Listet alle Dateien und Verzeichnisse eines P2P-Hyperdrives auf.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "p2p_drive_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoDer Hex-Key des Drives.
prefixNoOptionales Präfix / Verzeichnis (Standard: "/").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 implies a read-only listing but says nothing about permissions, whether the drive must already be connected/mounted, whether the listing is recursive, or what the result contains.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification for a tool that lists directory contents.

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

Completeness2/5

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

With no annotations, no output schema, and only a bare one-line description, an agent lacks the context it needs: whether a connection is prerequisite, what fields the listing returns, and whether the prefix recursion applies. The definition is thin for a listing operation whose output shape is undisclosed.

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 both 'key' and 'prefix' are already documented in the schema, giving a baseline of 3. The description adds no syntax, default, or format detail beyond what the schema provides.

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 ('Listet') and resource ('alle Dateien und Verzeichnisse eines P2P-Hyperdrives'), which clearly separates it from the read/write siblings p2p_file_read and p2p_file_write. It does not explicitly name an alternative, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites (e.g. whether the drive must first be connected via p2p_drive_connect), and no exclusions or alternatives. Usage is only loosely implied by the verb 'Listet'.

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