Skip to main content
Glama
henilcalagiya

io.github.henilcalagiya/mcp-apple-notes

read_folder

Read a specific Apple Notes folder by its primary key ID and verified name, returning metadata, child folders, notes, and summary counts.

Instructions

Read a folder by its primary key ID with AppleScript verification.

Security Features:

  • Verifies folder exists with the given ID and name

  • Uses primary key ID for precise identification

  • Returns detailed folder information with contents

Output:

  • Folder metadata (name, ID, creation/modification dates)

  • Direct child folders (names and IDs)

  • Notes in the folder (names and IDs)

  • Summary counts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesPrimary key ID of the folder to read (e.g., 'p2330')
folder_nameYesName of the folder to verify and read

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes verification process and output structure in detail, but lacks explicit statement that it is read-only (no side effects). Given no annotations, this is strong but not perfect.

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?

Well-structured into sections, every sentence adds value, no unnecessary content.

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?

Covers purpose, security, output structure; could mention relation to siblings like list_folder_with_structure, but adequate for a simple read tool.

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 100%, baseline 3; description adds purpose for both parameters (verification, precise ID) and why both are required.

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?

Clearly states the verb (read) and resource (folder), specifies use of primary key ID and verification, distinct from siblings like list_folder_with_structure.

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?

Implies usage for reading a specific folder with verification, but no explicit when-to-use vs alternatives or exclusions.

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/henilcalagiya/mcp-apple-notes'

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