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

apple-productivity-mcp

by gambadio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

apple_textedit_list_documents

Read-onlyIdempotent

List open TextEdit documents with pagination via limit and offset. Returns only currently open documents and does not launch TextEdit if it is closed.

Instructions

List open TextEdit documents. Does not launch a stopped application.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely non-annotation behavioral trait: it will not launch a stopped application, which tells the agent this call cannot bootstrap the app.

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?

Two short sentences, front-loaded with the core purpose and followed immediately by the key constraint. No filler or repetition of the name.

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?

For a paginated list tool with no output schema and zero parameter documentation, the description omits any mention of pagination or return shape. The app-launch caveat is valuable, but the listing mechanics an agent needs are missing.

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 description coverage is 0% and the description says nothing about the two parameters (limit, offset) or their defaults and bounds. It fails to compensate for the coverage gap, leaving pagination entirely undocumented outside the raw schema types.

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?

States a specific verb (List) and resource (TextEdit documents) with a scope qualifier ('open'). It is clearly distinguishable from the sibling document-listing tools for Pages, Numbers, and Keynote, which share the same verb but a different app.

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?

The second sentence implies a usage condition (the app must already be running for this to return anything), but it never explicitly routes the agent to an alternative such as apple_textedit_open when the app is stopped. The context is implied rather than 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