Skip to main content
Glama
aic0t

AI Coach MCP Server

by aic0t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search AI Coach memos

search_ai_coach_notes
Read-only

Find matching AI Coach memos by title or body text using case-insensitive substring search. Get snippets around hits, with optional filtering by group.

Instructions

Search the user's AI Coach memos by title and body text (case-insensitive substring). Returns matching memos with a snippet around the hit. Pass 'group' to search one group only, or an empty string for ungrouped memos. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNoSearch inside this group only. An empty string means ungrouped memos only. Omit to search all memos.
limitNoNumber of hits to return (default 20, max 50).
queryYesTerm matched case-insensitively against memo titles and body text.
localeNoDisplay language (BCP 47).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.4
    • changedInput schema / properties / locale / description
      Previous value: -"Display language hint (BCP 47). The dashboard view passes hostContext.locale through unchanged."New value: +"Display language (BCP 47)."
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "connection": {
-      "enum": [
-        "connected",
-        "app_unavailable",
-        "incompatible"
-      ],
-      "type": "string"
-    },
-    "deleted": {
-      "additionalProperties": false,
-      "properties": {
-        "deleted": {
-          "type": "boolean"
-        },
-        "noteId": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "noteId",
-        "deleted"
-      ],
-      "type": "object"
-    },
-    "error": {
-      "additionalProperties": false,
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "reason": {
-          "type": "string"
-        },
-        "retryable": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "code",
-        "retryable"
-      ],
-      "type": "object"
-    },
-    "folderName": {
-      "type": "string"
-    },
-    "groups": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "hits": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "group": {
-            "type": "string"
-          },
-          "modifiedAt": {
-            "type": "string"
-          },
-          "noteId": {
-            "type": "string"
-          },
-          "sizeBytes": {
-            "minimum": 0,
-            "type": "integer"
-          },
-          "snippet": {
-            "type": "string"
-          },
-          "title": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "noteId",
-          "title",
-          "modifiedAt",
-          "sizeBytes",
-          "snippet"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "note": {
-      "additionalProperties": false,
-      "properties": {
-        "content": {
-          "type": "string"
-        },
-        "modifiedAt": {
-          "type": "string"
-        },
-        "noteId": {
-          "type": "string"
-        },
-        "offsetBytes": {
-          "minimum": 0,
-          "type": "integer"
-        },
-        "returnedBytes": {
-          "minimum": 0,
-          "type": "integer"
-        },
-        "sizeBytes": {
-          "minimum": 0,
-          "type": "integer"
-        },
-        "title": {
-          "type": "string"
-        },
-        "truncated": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "noteId",
-        "title",
-        "modifiedAt",
-        "sizeBytes",
-        "content",
-        "offsetBytes",
-        "returnedBytes",
-        "truncated"
-      ],
-      "type": "object"
-    },
-    "notes": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "excerpt": {
-            "type": "string"
-          },
-          "group": {
-            "type": "string"
-          },
-          "modifiedAt": {
-            "type": "string"
-          },
-          "noteId": {
-            "type": "string"
-          },
-          "sizeBytes": {
-            "minimum": 0,
-            "type": "integer"
-          },
-          "title": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "noteId",
-          "title",
-          "modifiedAt",
-          "sizeBytes",
-          "excerpt"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "offset": {
-      "minimum": 0,
-      "type": "integer"
-    },
-    "protocolVersion": {
-      "const": 1,
-      "type": "number"
-    },
-    "total": {
-      "minimum": 0,
-      "type": "integer"
-    },
-    "updatedAt": {
-      "type": "string"
-    },
-    "written": {
-      "additionalProperties": false,
-      "properties": {
-        "created": {
-          "type": "boolean"
-        },
-        "group": {
-          "type": "string"
-        },
-        "modifiedAt": {
-          "type": "string"
-        },
-        "noteId": {
-          "type": "string"
-        },
-        "sizeBytes": {
-          "minimum": 0,
-          "type": "integer"
-        },
-        "title": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "noteId",
-        "title",
-        "created",
-        "modifiedAt",
-        "sizeBytes"
-      ],
-      "type": "object"
-    }
-  },
-  "required": [
-    "protocolVersion",
-    "connection",
-    "updatedAt"
-  ],
-  "type": "object"
-}New value: +null
  2. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces that with 'Read-only.' It adds meaningful behavioral detail beyond the annotations: case-insensitive substring matching, matching against title and body, and snippet-around-hit return behavior. No contradiction exists between the description and annotations.

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?

The description is three sentences and every sentence contributes distinct information: search scope, return behavior, and group filtering. It is front-loaded with the core verb and resource, with no filler or redundancy beyond a brief read-only confirmation.

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

Completeness4/5

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

For a search tool with four fully documented parameters and read-only annotations, the description is largely complete. It explains what is searched, how matching works, and what the response contains at a functional level. Since there is no output schema, a bit more detail about the exact return shape or ordering could help, but the description is sufficient for correct invocation.

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 the schema already fully documents all four parameters. The description reiterates group semantics and matching behavior but adds little beyond the schema. It earns the baseline 3 for not being harmful or misleading, but it does not elevate parameter understanding.

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?

The description uses a specific verb and resource: 'Search the user's AI Coach memos by title and body text (case-insensitive substring).' It clearly distinguishes the search behavior from sibling list/read tools by mentioning snippet-around-hit results. No ambiguity about what the tool does.

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?

The description gives concrete usage context for the 'group' parameter: search one group only, use empty string for ungrouped memos, and omit to search all. It also states the operation is read-only. However, it does not explicitly compare this tool with alternatives like list_ai_coach_notes or read_ai_coach_note, so it stops short of full when-to-use-vs-alternatives guidance.

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