Skip to main content
Glama
arslankhanali

Apple Notes MCP Server

list_accounts

Retrieve all available Apple Notes accounts to manage notes across different user profiles or iCloud configurations.

Instructions

List all available Notes accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'list_accounts' tool, decorated with @mcp.tool() which also serves as registration. It runs an AppleScript to list Notes accounts, parses the output, and formats it nicely.
    @mcp.tool()
    async def list_accounts() -> str:
        """List all available Notes accounts."""
        script = '''
        tell application "Notes"
            set accountList to {}
            repeat with anAccount in accounts
                set end of accountList to name of anAccount
            end repeat
            return accountList
        end tell
        '''
        
        output, success = run_applescript(script)
        if not success:
            return output
        
        if not output or output == "{}":
            return "No accounts found."
        
        accounts = [acc.strip().strip('"').strip("'") for acc in output.split(", ")]
        
        result = "Available accounts:\n"
        for i, account in enumerate(accounts, 1):
            result += f"{i}. {account}\n"
        
        return result
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists accounts but doesn't describe traits like pagination, sorting, filtering, authentication needs, rate limits, or response format. For a read operation with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that directly states the tool's purpose without redundancy. It is front-loaded with the core action and resource, making it easy to parse. Every word earns its place, with no wasted verbiage.

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?

Given the tool's simplicity (0 parameters, read-only operation) and the presence of an output schema, the description is minimally adequate. However, it lacks behavioral context like how accounts are returned or any constraints, which could be helpful despite the output schema. For a basic list tool, it meets the minimum but doesn't excel.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, aligning with the schema. A baseline of 4 is applied since no parameters exist, and the description doesn't add unnecessary information.

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 clearly states the action ('List') and resource ('Notes accounts'), making the purpose understandable. It distinguishes from siblings like 'list_notes' by specifying accounts rather than notes, though it doesn't explicitly contrast them. The verb+resource combination is specific but lacks explicit sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_notes' or other account-related operations. The description implies usage for retrieving accounts but doesn't specify contexts, prerequisites, or exclusions. This leaves the agent without direction on appropriate application scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arslankhanali/apple-notes-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server