Skip to main content
Glama
Sign In
droidmcp

droidmcp

by 846572691
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

storage

Check free and used space on an Android device's /data partition, optionally specifying the device serial when multiple devices are connected.

Instructions

Free/used storage for the /data partition.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial from list_devices (omit when exactly one device is connected).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It implies a read-only query but says nothing about return format (bytes, percent, used vs free breakdown) or what happens when the device argument is omitted and multiple devices are attached.

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 short sentence with zero waste, and the scope qualifier (/data partition) is front-loaded. It is appropriately terse for a simple query tool.

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 one-parameter, no-output-schema read tool, the description covers the subject but not the return shape or units. Adequate but with a clear gap for an agent trying to interpret results.

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 coverage is 100% and the single optional device parameter is fully documented in the schema, including the omit-when-one-device rule. The description adds nothing beyond that, so the baseline 3 applies.

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 resource (storage) and narrows it to the /data partition, so the agent knows exactly what is measured. The verb is implied rather than stated and it does not reference siblings, but none of the siblings overlap with this concern, so confusion is unlikely.

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?

There is no when-to-use guidance and no alternatives named. The agent can infer this is a read-only storage check, but the description never says when this is preferable to device_info or battery.

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