Skip to main content
Glama
Neboy72

Nexus Memory

by Neboy72
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

subscribe

Register a webhook URL to get HTTP POST notifications for memory events (remember, update, or forget), and receive a subscription ID for later cancellation.

Instructions

Register a webhook URL to receive HTTP POST notifications when a memory event of the given type fires. Returns the subscription id (UUID) which you need to unsubscribe. Subscriptions are stored in ~/.nexus-webhooks.json and survive server restarts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_typeYesEvent to subscribe to. One of: 'memory.remember' (after a new memory is stored), 'memory.update' (after a memory is updated in place), 'memory.forget' (after a memory is deleted).
webhook_urlYesThe http:// or https:// URL that will receive the JSON POST payload {event, memory_id, timestamp}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.18.7
    • changedInput schema / properties / event_type / enum
      Previous value: -[
-  "memory.remember",
-  "memory.update",
-  "memory.forget"
-]New value: +[
+  "memory.remember",
+  "memory.update",
+  "memory.forget",
+  "fuel.exhausted"
+]
  2. First observedv0.13.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently states that subscriptions persist in ~/.nexus-webhooks.json and survive server restarts, and that the tool returns a UUID needed for unsubscribing. It does not mention duplicate-subscription handling or authorization requirements, but the core side effects are clearly disclosed.

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?

Three sentences, each carrying unique information: the registration action, the return value, and the persistence behavior. The description is front-loaded with the main purpose and contains no filler.

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?

The tool is simple with two parameters, a full schema, and no output schema. The description covers the return value and persistence behavior, which are the main non-schema facts needed to call it correctly. Minor gaps remain around failure modes and duplicate subscription behavior, but they do not block correct usage.

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?

The schema describes both parameters completely, so the baseline is 3. The description adds useful context about the webhook receiving HTTP POST notifications and the returned subscription ID, but it does not add substantial parameter-level meaning beyond what the schema already provides.

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-resource pair: 'Register a webhook URL' to receive notifications for a specified memory event. It clearly differentiates this from sibling tools like unsubscribe and list_subscriptions by framing it as the subscription-creation operation.

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

Usage Guidelines3/5

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

The description implies the intended use case—registering a webhook to receive memory event notifications—but it does not explicitly state when to choose this tool over alternatives. The line 'which you need to unsubscribe' hints at the counterpart tool but does not provide explicit when-to-use versus when-not-to-use 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