Skip to main content
Glama
CalebChristiansen

Memoreei

by CalebChristiansen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_sources

Read-only

Who is in the archive: the most-messaged people with their chats, the busiest group chats, and the platforms.

Instructions

Who is in the archive: the most-messaged people with their chats, the busiest group chats, and the platforms.

Not needed before searching: search_memoreei finds people by name or number itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOnly people and groups whose name matches, like participant does ('Jane', 'jan do').
limitNoHow many people, and how many groups. Default 30.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
totalYes
groupsYes
peopleYes
not_shownNo
platformsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.7
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 30,
+  "description": "How many people, and how many groups. Default 30.",
+  "maximum": 200,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only people and groups whose name matches, like participant does ('Jane', 'jan do').",
+  "title": "Name"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "GroupSource": {
+      "properties": {
+        "messages": {
+          "title": "Messages",
+          "type": "integer"
+        },
+        "name": {
+          "title": "Name",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "source",
+        "messages"
+      ],
+      "title": "GroupSource",
+      "type": "object"
+    },
+    "PersonSources": {
+      "properties": {
+        "messages": {
+          "title": "Messages",
+          "type": "integer"
+        },
+        "name": {
+          "title": "Name",
+          "type": "string"
+        },
+        "sources": {
+          "additionalProperties": {
+            "type": "integer"
+          },
+          "description": "Each chat's source id and its message count",
+          "title": "Sources",
+          "type": "object"
+        }
+      },
+      "required": [
+        "name",
+        "messages",
+        "sources"
+      ],
+      "title": "PersonSources",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "groups": {
+      "items": {
+        "$ref": "#/$defs/GroupSource"
+      },
+      "title": "Groups",
+      "type": "array"
+    },
+    "not_shown": {
+      "anyOf": [
+        {
+          "additionalProperties": {
+            "type": "integer"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Not Shown"
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Note"
+    },
+    "people": {
+      "items": {
+        "$ref": "#/$defs/PersonSources"
+      },
+      "title": "People",
+      "type": "array"
+    },
+    "platforms": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Platforms",
+      "type": "array"
+    },
+    "total": {
+      "title": "Total",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "platforms",
+    "people",
+    "groups"
+  ],
+  "title": "Sources",
+  "type": "object"
+}
  2. First observedv0.2.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds that results are ordered by message volume and split across people/groups/platforms, but this is essentially return-content detail also covered by the output schema, so it adds limited behavioral context beyond 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?

Two short sentences with zero waste, and the routing constraint is front-loaded in the second line. Nothing redundant or padded.

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?

With an output schema present, return values need not be explained, and annotations cover safety. The description supplies purpose and usage context adequately, though the meaning of 'sources' relies partly on the annotation title ('List people and chats').

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 'name' (partial match, like participant) and 'limit' (default 30, max 200) are already fully documented in the schema. The description adds no parameter detail beyond it, so the baseline 3 applies.

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

Purpose4/5

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

The description defines what list_sources returns: the most-messaged people with their chats, busiest group chats, and platforms. It conveys the resource concretely, though it is phrased as a label ('Who is in the archive') rather than a clean verb+resource, and it doesn't explicitly contrast against other listing-type siblings.

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?

It states when the tool is NOT needed ('Not needed before searching') and names the alternative that handles the case instead (search_memoreei finds people by name or number itself). This is explicit routing guidance an agent can act on directly.

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