Skip to main content
Glama
Sign In
Alcove

Alcove

Official
by OctopusGarage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

alcove_connector_apple_notes_index

Index Apple Notes export directories to integrate notes into Alcove for search and access.

Instructions

Index a deterministic Apple Notes export directory.

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": {
      "export_dir": "<export_dir>"
    },
    "name": "alcove_connector_apple_notes_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeNo
tagsNo
workspaceNo
export_dirYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. The term 'deterministic' is ambiguous and no other behaviors (e.g., side effects, permissions, or idempotency) are mentioned. This is insufficient for safe and correct invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) but this brevity comes at the cost of clarity and completeness. While it is front-loaded, it does not earn its place as it lacks necessary detail.

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 having an output schema, the description does not explain the return value or how the index operation fits into the overall workflow. Given the complexity and the large set of sibling tools, the description is incomplete and leaves many questions unanswered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description adds no explanation of parameters. The tool has 4 parameters (home, tags, workspace, export_dir) but their roles and interactions are not clarified. The description fails to compensate for poor schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Index a deterministic Apple Notes export directory' which provides a verb and resource, but 'index' is vague and not clearly distinguished from sibling tools like alcove_connector_apple_notes_import_local. The purpose is somewhat clear but lacks specificity.

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 given on when to use this tool versus alternatives. With a closely related sibling (import_local), the absence of usage context makes it difficult for an agent to decide when to choose index over import.

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