Skip to main content
Glama
Sign In

Lemma Telepath

by company.lemma
OverviewDiscussionsAdmin

Create a note

kb_create_note
Destructive

Save a new note to your knowledge base. Titles are unique; if one exists, use kb_update_note instead. The body is markdown and may reference other notes with [[Title]]. Tags help you find it later. An optional reminder on a task schedules a future Telegram bot message to the account owner; only set it with user authorization. It shares the creation allowance with standalone reminders; entitlement_required means the save did not happen.

Input Schema

NameRequiredDescriptionDefault
bodyNoMarkdown body. May contain [[links]] to other notes.
tagsNoTags, e.g. ["work", "idea"].
typeNoPage type. Existing pages keep their type if omitted. Only tasks support attached reminders. Standalone reminders use create_reminder.
titleYesUnique title for the note.
reminderNoOnly with user authorization: schedule one Telegram bot DM to the account owner. Null cancels; omitted preserves the existing reminder. Never infer a reminder from a task or date alone.
task_statusNoTask status. Completing a task cancels its pending reminder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / description
      Previous value: -"Page type. Existing pages keep their type if omitted. Only tasks support reminders (Plus or Unlimited)."New value: +"Page type. Existing pages keep their type if omitted. Only tasks support attached reminders. Standalone reminders use create_reminder."
  2. Changed1 schema field changed
    • changedInput schema / properties / type / description
      Previous value: -"Page type. Existing pages keep their type if omitted. Only tasks support reminders."New value: +"Page type. Existing pages keep their type if omitted. Only tasks support reminders (Plus or Unlimited)."
  3. Changed3 schema fields changed
    • addedInput schema / properties / reminder
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "at": {
+          "description": "Exact future ISO 8601 time with Z or UTC offset. Ask if the intended time or timezone is unclear.",
+          "type": "string"
+        },
+        "text": {
+          "description": "The specific reminder text authorized by the user, in their language.",
+          "maxLength": 1500,
+          "minLength": 1,
+          "type": "string"
+        },
+        "timezone": {
+          "description": "User-confirmed IANA timezone, for example Europe/Samara.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "at",
+        "timezone",
+        "text"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Only with user authorization: schedule one Telegram bot DM to the account owner. Null cancels; omitted preserves the existing reminder. Never infer a reminder from a task or date alone."
+}
    • addedInput schema / properties / task_status
      Added value: +{
+  "description": "Task status. Completing a task cancels its pending reminder.",
+  "enum": [
+    "open",
+    "done"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Page type. Existing pages keep their type if omitted. Only tasks support reminders.",
+  "enum": [
+    "note",
+    "project",
+    "person",
+    "task"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare mutation, destructive, non-idempotent and open-world behavior, so the bar is lower, yet the description still adds non-obvious facts: titles are unique so duplicates fail rather than overwrite, reminders dispatch a real Telegram DM to the account owner, and 'entitlement_required' signals the save did not happen. It stops short of stating what a successful save returns or whether storing a reminder is irreversible once scheduled.

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

Conciseness4/5

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

Five short sentences, front-loaded with the core action and the duplicate-title exception. A couple of clauses echo the schema's own parameter descriptions, which is mild redundancy but not bloat.

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 six-parameter mutation tool with no output schema, it covers the important traps: uniqueness collision, reminder authorization, shared quota, and a failure sentinel. The main omission is what a successful creation returns (e.g., a note identifier) so the agent can chain into kb_update_note or kb_get_note.

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 alone documents body/[[links]], tags and the type enum, and the description largely restates the markdown-link and tags points. Its marginal additions (shared creation allowance, entitlement_required) are behavioral rather than parameter-level detail.

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?

Opens with a specific verb and resource ('Save a new note to your knowledge base') and immediately differentiates itself from the sibling kb_update_note by the uniqueness rule. An agent can tell exactly which tool handles new-note creation.

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

Usage Guidelines5/5

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

Explicitly states the branch condition ('Titles are unique; if one exists, use kb_update_note instead') and names the sibling to use in that case. It also gates the reminder feature on user authorization, so the agent knows both when to use this tool and when to defer or ask.

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

All Lemma Telepath toolsInspect
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.

Resources