Skip to main content
Glama
Sign In
hyperdrive-mesh

hyperdrive-mesh

by tastenkasperle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

p2p_swarm_status

Check the status of all mounted drives and count active P2P peers in the Hyperswarm network.

Instructions

Liefert den aktuellen Status aller gemounteten Drives und die Anzahl aktiver P2P-Peers im Hyperswarm.

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_swarm_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. A 'Status liefern' operation is implicitly a read-only, side-effect-free query, but the description never states this, nor mentions auth needs or rate limits. For a zero-param diagnostic tool the risk is low, so a 3 is fair rather than a severe gap.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; it states exactly what is returned and nothing more.

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?

With no output schema, the description must describe the return payload. It names the two top-level items (drive statuses, peer count) but leaves 'Status' undefined — no fields, units, or shape — so an agent cannot fully anticipate the response.

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

Parameters4/5

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

The tool takes no parameters, so there is no parameter semantics to convey; the baseline for zero-param tools is 4.

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 ('Liefert') and two concrete resources: the status of all mounted drives and the count of active P2P peers in the Hyperswarm. An agent can distinguish it from p2p_drive_list (which lists drives) because this one reports status plus swarm peer count, 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 Guidelines2/5

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

No guidance on when to call this versus the overlapping sibling p2p_drive_list, and no prerequisites or context (e.g. 'use to diagnose connectivity'). The agent must infer usage entirely from the purpose.

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