Skip to main content
Glama

phone_send_files

Transfer files from your computer to an Android phone using absolute paths. Files are saved to Downloads/Agent Bridge and work over Wi-Fi or USB.

Instructions

Send files from this computer to the phone (absolute paths). They are saved in Downloads/Agent Bridge on the phone. Works over Wi-Fi or USB.

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": {
      "paths": "<paths>"
    },
    "name": "phone_send_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden and does contribute real facts: the destination folder 'Downloads/Agent Bridge on the phone' and the supported transports. It does not disclose overwrite behavior, size limits, error conditions, or what the tool returns, all of which matter for a file-mutation operation.

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?

Three compact clauses: action and argument constraint first, destination second, transport third. Nothing is repeated or wasted.

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?

For a one-parameter, no-annotation, no-output-schema tool this covers the essentials: what moves, where it lands, and the required path format. Missing return/confirmation details are a minor gap given the tool's simplicity.

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?

Schema coverage is 0% and the single parameter is only typed as an array of strings, so the description's '(absolute paths)' constraint is genuinely additive information an agent would otherwise not have. It still says nothing about multiple-file handling or path separators, keeping it short of a 5.

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?

Uses a specific verb ('Send files') plus explicit direction ('from this computer to the phone'), which makes the transfer direction unambiguous. It does not name a sibling or distinguish itself from phone_received_files, but the direction alone effectively separates the two.

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 'Works over Wi-Fi or USB' note establishes transport context but gives no guidance on when to prefer this tool or when it is unavailable. Usage is implied rather than stated, with no exclusions or prerequisites such as the phone needing the Agent Bridge app.

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