justdrop-mcp

Check a transfer

status

Track live peer presence, per-file progress, saved paths, and errors for your JustDrop transfers. Omit room code to see all active transfers.

Instructions

Shows the live status of a JustDrop transfer started with drop or receive: peer presence, per-file progress, saved paths, and errors. Call with no room_code to list all transfers in this session.

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": "status"
  }
}

Input Schema

Name	Required	Description	Default
`room_code`	No	Room code returned by drop/receive

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Jul 26, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It describes the data shown but does not explicitly state it is read-only, nor does it disclose any behavioral traits like rate limits or authentication. The implication is non-destructive, but could be more explicit.

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?

Two sentences; no redundant words. Front-loaded with the main action and details, then calling modes. Every sentence earns its place.

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

Completeness4/5

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

Given the simple tool (one optional param, no output schema), the description covers the key aspects: what status information is included and how to call. It does not detail the output format, but lists contents, which is sufficient.

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?

Parameter schema has 100% coverage describing room_code. The description adds context that omitting room_code lists all transfers, which adds value beyond the schema.

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

Purpose5/5

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

Description clearly states it shows live status of a JustDrop transfer and lists included details (peer presence, per-file progress, saved paths, errors). It also distinguishes two calling modes, making the purpose precise and unambiguous.

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

Usage Guidelines4/5

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

Description explains when to use the tool (after drop or receive) and how to call it with or without room_code. Since there are no sibling tools, no explicit when-not-to is needed, but it could include a note about prerequisites.

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

statusA