Skip to main content
Glama
CalebChristiansen

Memoreei

by CalebChristiansen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sync_signal

Import your Signal Desktop messages into Memoreei's searchable memory. Sync texts, captions, links, and calls after a one-time Signal connection.

Instructions

Sync Signal from Signal Desktop's database on this computer.

Needs Signal connected first (the dashboard's Sources page, or memoreei setup signal), which reads Signal's database key from the system keyring once. Texts, captions, links, group changes and calls are kept, reactions and edits follow the message they belong to, and disappearing messages are never stored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.4
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Conversation Id"
-}
  2. First observedv0.2.2

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well. It discloses the required Signal connection and keyring read, exactly what data is kept (texts, captions, links, group changes, calls), how reactions/edits are handled, and that disappearing messages are never stored.

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 tight sentences: purpose first, then prerequisite/setup, then retention behavior. Every sentence adds useful information and there is no filler or repetition.

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?

Given no parameters, no output schema, and no annotations, the description covers purpose, setup requirements, and data handling policies thoroughly. An agent has enough context to know when and how to invoke it without needing additional structured fields.

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?

The tool takes zero parameters, so there are no parameter semantics for the description to clarify. The baseline for a parameterless tool is 4, and the description appropriately does not invent or omit parameter details.

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 states a specific verb and resource: 'Sync Signal from Signal Desktop's database on this computer.' It names the source platform and local database, which distinguishes it from sibling sync tools for WhatsApp, Discord, Telegram, etc. without ambiguity.

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?

It gives a clear prerequisite: Signal must be connected first via the dashboard Sources page or `memoreei setup signal`. This tells the agent when the tool can actually be used, but it does not explicitly contrast this tool with alternatives like sync_all or other sync_* tools.

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