Skip to main content
Glama
Sign In
nucleus-apple-mcp

nucleus-apple-mcp

by zish-rob-crur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

notes.add_attachment

Add attachments to a note from local file paths. Specify note ID and one or more file paths.

Instructions

Add attachment(s) to a note from local file paths.

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": {
      "note_id": "<note_id>",
      "attach_file": "<attach_file>"
    },
    "name": "notes.add_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYesNote identifier.
attach_fileYesLocal file path to attach (repeatable).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It does not disclose behavior such as overwriting, error handling, or permissions. The output schema exists but is not referenced.

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?

Single sentence that conveys the essential purpose with no unnecessary words. Properly front-loaded.

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

Completeness2/5

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

Despite lacking annotations, the description omits important context for a mutation tool: idempotency, conflict behavior, file existence handling. The distinction from notes.save_attachment is unclear.

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?

Schema coverage is 100% but descriptions are minimal. The tool description adds little beyond 'from local file paths', which is already in attach_file's description. No additional constraints or examples.

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 (add attachment) and resource (note) with the source (local file paths). It distinguishes from sibling tools like notes.save_attachment, but could be more explicit about when to use which.

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 on when to use this tool versus alternatives like notes.save_attachment or prerequisites. The description does not specify context or conditions.

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