Skip to main content
Glama

phone_received_files

Lists files the user sent from an Android phone to this computer, newest first, with folder paths so you can open or read them.

Instructions

Files the user sent from the phone to this computer (newest first) and the folder they are in, so you can open or read them.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses result ordering (newest first) and that folder locations are returned, but says nothing about permissions, how many results come back by default, pagination, or behavior when no files exist.

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?

One sentence, front-loaded with the resource and never padded. The parenthetical ordering detail is placed well. Minor awkwardness in 'and the folder they are in' but nothing wasteful.

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 simple read tool with one parameter and no output schema, the description covers what is returned at a high level (files plus folder) and the sort order. It is still incomplete on the limit parameter and default result size, which matter for calling it correctly.

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

Parameters2/5

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

The single parameter 'limit' has 0% schema description coverage and is never mentioned in the description. An agent gets no hint that the result count can be capped or what the default cap is, so the description fails to compensate for the schema gap.

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?

The description names a specific resource and scope: files transferred from the phone to this computer, plus their containing folder, with an explicit ordering (newest first). It is clearly a retrieval tool, though it never names the counterpart phone_send_files, so the send-vs-list distinction is left implicit.

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 trailing clause 'so you can open or read them' implies the intended follow-up (read the returned paths), which is useful context. However, there is no explicit when-to-use/when-not guidance, no mention of alternatives, and no indication of what to do if the list is empty or truncated.

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