Keeploop

Create notes monitor

create_notes_monitor

Watch the user's Apple Notes. Fires on a new or changed note once it has been still for two minutes. title_contains matches the title, body_contains the title and text; give at least one. folder keeps it to one folder. Stops after ttl_hours or max_hits matches. Returns a token for check_monitor and cancel_monitor. It only records and notifies; it never sends, changes or deletes anything. routes tags the monitor for check_route; use 'duet:' for a Claude Duet channel so any later session there can read it. Requires Keeploop Pro.

Input Schema

Name	Required	Description
`name`	No	A short name for the monitor.
`folder`	No	Only notes in this folder (part of its name or path, e.g. Work).
`routes`	No	Up to 8 labels check_route reads this monitor's matches by, e.g. 'duet:fissler'. Lowercase letters, digits, '.', '_', ':' and '-'. A new monitor with routes has no Mac banner or ntfy push.
`max_hits`	No	Stop after this many matches; 1 for a one-shot watch.
`match_all`	No	Every new or changed note (needs routes).
`ttl_hours`	No	Stop after this many hours (default 24; no upper limit). 0 means no end: use it only when the user asks for a monitor that keeps running.
`body_contains`	No	Note title or text contains this.
`title_contains`	No	Title contains this.

Output Schema

Name	Required	Description	Default
`note`	No
`monitor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

addedInput schema / properties / folder

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only notes in this folder (part of its name or path, e.g. Work).",
+  "title": "Folder"
+}

addedInput schema / properties / match_all

Added value: +{
+  "default": false,
+  "description": "Every new or changed note (needs routes).",
+  "title": "Match All",
+  "type": "boolean"
+}

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / routes / description

Previous value: -"Up to 8 labels check_route reads this monitor's matches by, e.g. 'duet:fissler'. Lowercase letters, digits, '.', '_', ':' and '-'."New value: +"Up to 8 labels check_route reads this monitor's matches by, e.g. 'duet:fissler'. Lowercase letters, digits, '.', '_', ':' and '-'. A new monitor with routes has no Mac banner or ntfy push."

Changed4 schema fields changedOct 28, 2026

changedInput schema / properties / ttl_hours / description

Previous value: -"Stop after this many hours (default 24, max 720)."New value: +"Stop after this many hours (default 24; no upper limit). 0 means no end: use it only when the user asks for a monitor that keeps running."

addedOutput schema / $defs / MonitorInfo / properties / moved_from

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Moved From"
+}

addedOutput schema / $defs / MonitorInfo / properties / other_worktree_monitors

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Other Worktree Monitors"
+}

addedOutput schema / $defs / MonitorInfo / properties / other_worktree_note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Other Worktree Note"
+}

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / routes

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Up to 8 labels check_route reads this monitor's matches by, e.g. 'duet:fissler'. Lowercase letters, digits, '.', '_', ':' and '-'.",
+  "title": "Routes"
+}

addedOutput schema / $defs / MonitorInfo / properties / routes

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Routes"
+}

Changed2 schema fields changedOct 16, 2026

addedOutput schema / $defs / MonitorInfo / properties / commitments

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Commitments"
+}

addedOutput schema / $defs / MonitorInfo / properties / track

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Track"
+}

AddedOct 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: debounce behavior (fires once still for two minutes), lifecycle limits via ttl_hours/max_hits, return token, non-mutating scope ('only records and notifies; never sends, changes or deletes'), route behavior, and Pro requirement. These are meaningful operational details for an agent.

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?

Front-loads the core action ('Watch the user's Apple Notes') and then packs matching rules, lifecycle, return token, safety scope, routing, and auth requirement into dense, useful sentences. No filler.

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

Completeness5/5

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

For an 8-parameter optional monitor-creation tool with an output schema, the description covers matching semantics, stopping conditions, routing, lifecycle token usage, non-destructive behavior, and Pro requirement. Nothing essential for correct invocation is missing.

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%, so the baseline is 3. The description still adds cross-parameter meaning: at least one of title_contains/body_contains must be supplied, routes can use 'duet:<channel>', and match_all needs routes, which helps avoid invalid calls.

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 and resource: watch the user's Apple Notes and create a monitor that fires on new or changed notes. It clearly distinguishes this from email/calendar monitor siblings by naming Apple Notes and explaining the still-for-two-minutes trigger.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditions: provide at least one of title_contains/body_contains, use folder to scope, stop via ttl_hours/max_hits, and use the returned token with check_monitor/cancel_monitor. It also mentions routes and check_route, but does not explicitly state when to prefer this over create_email_monitor or create_calendar_monitor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Keeploop tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.