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

apple-notifier-mcp

by turlockmike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

select_file

Open a native file picker dialog to select files from your Mac. Specify prompt, default location, file types, and allow multiple selection.

Instructions

Open native file picker dialog

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": "select_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptNoOptional prompt message
defaultLocationNoOptional default directory path
fileTypesNoOptional file type filter (e.g., {"public.image": ["png", "jpg"]})
multipleNoWhether to allow multiple selection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations present, so description must carry full burden. It only says 'Open native file picker dialog', omitting behavior like blocking, return values, cancellation handling, or permissions.

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 is appropriately sized and front-loaded, no extraneous content.

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?

Lacks explanation of return value or behavior for a tool with no output schema and no annotations. Does not cover user interaction results.

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 description coverage is 100%, so baseline 3 applies. The description adds no additional meaning beyond what the schema already provides for each parameter.

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?

Description clearly states verb 'Open' and resource 'native file picker dialog', distinguishing it from sibling tools like prompt_user, send_notification, etc.

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; no when-not-to-use or context provided.

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