icloud-mcp

icloud_info

Retrieve metadata for a specified iCloud Drive file or folder, including local sync state, to verify availability before reads, writes, or moves.

Instructions

Metadata for one file or folder, including its local sync state.

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": {
      "path": "<path>"
    },
    "name": "icloud_info"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A3.5/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 burden, and it does disclose that the result includes local sync state — genuinely useful context beyond the schema. It does not state that this is a read-only/non-mutating operation, nor any failure behavior for missing or remote-only paths.

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 zero filler. Every clause (single item, local sync state) earns its place.

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?

An output schema exists, so return values need not be explained, and the tool is simple with one parameter. Still, path semantics are undocumented and there is no annotation coverage to compensate, leaving an agent to guess path format.

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 0% and the single 'path' parameter has no description anywhere. The phrase 'one file or folder' tells the agent the path addresses a single item, but nothing clarifies path format, roots, or whether it is local vs iCloud-relative.

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 the resource (metadata for a single file or folder) and adds a distinguishing detail (local sync state) that separates it from account-level siblings like icloud_status. The verb is implicit in the name rather than spelled out, but an agent can still tell it apart from icloud_list and icloud_search.

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?

Use is implied by 'for one file or folder' — you supply a path when you need metadata on a single item rather than a listing. However, it never states when to prefer this over icloud_status or icloud_list, nor any prerequisites or exclusions.

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

Deploy Server