Skip to main content
Glama
Sign In
icloud-docs-mcp

icloud-docs-mcp

by js713-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

status

Verify that your Apple ID session is trusted and iCloud Drive is reachable before browsing, searching, or downloading files.

Instructions

Check whether the Apple ID session is trusted and iCloud Drive is reachable.

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

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of disclosing behavior. 'Check' implies a read-only, non-destructive operation, but it does not mention potential side effects, return format, or any error handling. It does not describe what happens if the session is not trusted or iCloud Drive is unreachable, leaving some ambiguity.

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?

The description is a single, focused sentence that immediately states the purpose. It is concise, with no redundant words, and the key action and targets are front-loaded.

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

Completeness5/5

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

The tool is simple with no parameters and an output schema exists (not shown but referenced in context). The description adequately explains what the tool checks, which is sufficient for an agent to decide to call it. Since output schema covers return values, the description need not elaborate further.

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?

The tool has zero parameters, so the baseline is 4. The schema coverage is trivially 100% with no parameters to describe. The description does not need to add parameter semantics since none exist.

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?

The description clearly states the tool's purpose with a specific verb 'Check' and identifies the resources: 'Apple ID session' and 'iCloud Drive'. It specifies the checks performed (trusted, reachable), distinguishing it from sibling tools that handle listing, searching, downloading, or reading text.

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?

The description provides no guidance on when to use this tool versus alternatives or when not to use it. It does not mention prerequisites, typical scenarios, or relationship to sibling tools. The purpose implies it might be used before other operations, but this is not explicitly stated.

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