Skip to main content
Glama

smry Product

by ai.smry.r
OverviewDiscussionsAdmin

manage feed consumers (create/list/ack/delete)

manage_feed_consumers
Destructive

create: Save a where predicate and let smry retain one processing checkpoint. New consumers start at the current high-water mark, so they receive future discoveries rather than replaying history. For history, create the Consumer first, query the historical window separately, then poll; that order closes the query/create race. Create one per independent processing loop, not per source. Retrying the same case-insensitive name and predicate returns the existing Consumer; the same name with another predicate is a 409. Required fields: name. Example: {"action":"create","name":"Engineering briefing","where":{"collection":["Research"]}} list: List each saved consumer, its opaque acknowledged_cursor, delivery and acknowledgement timestamps, and how many matching entries are waiting past that checkpoint. Required fields: none. Example: {"action":"list"} ack: After processing every event returned by getFeedChanges for this consumer, acknowledge that response's next_cursor. Crashes before ack cause safe redelivery; stale, foreign, and invented cursors are rejected. Required fields: id, cursor. Example: {"action":"ack","id":7,"cursor":""} delete: Remove only the saved predicate and checkpoint. Followed sources, entries, and human read state are untouched. Required fields: id. Example: {"action":"delete","id":7}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
whereNoEntry selection predicate: fields AND together; omit a field to not filter on it. Source queries/mutations accept only collection and source; use query having for source-health filters.
actionYes"create": Create a managed feed consumer · "list": List managed consumers with pending counts · "ack": Acknowledge a managed consumer batch · "delete": Delete a managed feed consumer
cursorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / where / properties / discovered_after / description
      Previous value: -"Relative window (\"7d\", \"36h\", \"45m\", \"2w\") or ISO date."New value: +"When smry first saw the entry. Backfill makes old posts look new here, so use it for diffs, not for \"what's new\". Relative window (\"7d\", \"36h\", \"45m\", \"2w\"), \"now\", or ISO date."
    • changedInput schema / properties / where / properties / discovered_before / description
      Previous value: -"Relative window (\"7d\", \"36h\", \"45m\", \"2w\") or ISO date."New value: +"Relative window (\"7d\", \"36h\", \"45m\", \"2w\"), \"now\", or ISO date."
    • changedInput schema / properties / where / properties / published_after / description
      Previous value: -"Relative window (\"7d\", \"36h\", \"45m\", \"2w\") or ISO date."New value: +"When the source published the entry (entries with no publish date are excluded; use top-level since to include them). Relative window (\"7d\", \"36h\", \"45m\", \"2w\"), \"now\", or ISO date."
    • changedInput schema / properties / where / properties / published_before / description
      Previous value: -"Relative window (\"7d\", \"36h\", \"45m\", \"2w\") or ISO date."New value: +"Relative window (\"7d\", \"36h\", \"45m\", \"2w\"), \"now\", or ISO date."
    • changedInput schema / properties / where / properties / source / properties / exclude / items / description
      Previous value: -"A source id (from any v2 response) or its exact title."New value: +"A source id (from any v2 response) or its title. Reads also accept a fragment that matches exactly one title."
    • changedInput schema / properties / where / properties / source / properties / include / items / description
      Previous value: -"A source id (from any v2 response) or its exact title."New value: +"A source id (from any v2 response) or its title. Reads also accept a fragment that matches exactly one title."
  2. Changed12 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / id / anyOf
      Removed value: -[
-  {
-    "default": 0,
-    "type": "string"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": 1,
-    "type": "integer"
-  }
-]
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / id / minimum
      Added value: +1
    • addedInput schema / properties / id / type
      Added value: +"integer"
    • changedInput schema / properties / where / description
      Previous value: -"Selection predicate shared by every feeds operation. All fields AND together; omit a field to not filter on it."New value: +"Entry selection predicate: fields AND together; omit a field to not filter on it. Source queries/mutations accept only collection and source; use query having for source-health filters."
    • changedInput schema / properties / where / properties / collection / items / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "default": 0,
-        "type": "string"
-      },
-      {
-        "maximum": 9007199254740991,
-        "minimum": 1,
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "maxLength": 100,
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  }
+]
    • addedInput schema / properties / where / properties / collection / minItems
      Added value: +1
    • changedInput schema / properties / where / properties / source / properties / exclude / items / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "default": 0,
-        "type": "string"
-      },
-      {
-        "maximum": 9007199254740991,
-        "minimum": 1,
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "maxLength": 500,
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "maxLength": 500,
+    "minLength": 1,
+    "type": "string"
+  }
+]
    • addedInput schema / properties / where / properties / source / properties / exclude / minItems
      Added value: +1
    • changedInput schema / properties / where / properties / source / properties / include / items / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "default": 0,
-        "type": "string"
-      },
-      {
-        "maximum": 9007199254740991,
-        "minimum": 1,
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "maxLength": 500,
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "maxLength": 500,
+    "minLength": 1,
+    "type": "string"
+  }
+]
    • addedInput schema / properties / where / properties / source / properties / include / minItems
      Added value: +1
  3. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations only convey read-only/destructive hints, so the description carries the behavioral burden. It adds meaningful details: new consumers start at the current high-water mark, crashes before ack cause safe redelivery, stale/foreign/invented cursors are rejected, and delete does not affect followed sources, entries, or read state. No contradiction with 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 longer than average, but the four-action structure justifies it: each section follows a consistent pattern of purpose, key semantics, required fields, and an example. There is no filler or redundant restatement of the schema.

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 the tool's four distinct operations, the description covers the essential behavioral details: high-water mark behavior, race avoidance, redelivery safety, idempotency, error conditions, and required parameters per action. An output schema exists, so return-value details are not required. The only minor blemish is the internal use of 'getFeedChanges' instead of the sibling tool name 'get_feed_changes', but the meaning is unambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%, but the description compensates well by stating the required fields for each action and providing concrete JSON examples. It gives extra meaning to cursor as the next_cursor from get_feed_changes and to name as case-insensitive with retry semantics, while the schema already documents the nested where filter fields.

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 is organized by the four actions—create, list, ack, delete—each with a specific verb and target resource. It cleanly distinguishes ack as acknowledging a get_feed_changes cursor and delete as removing only the saved predicate and checkpoint, so an agent can differentiate actions without opening the schema.

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?

The description gives explicit workflow guidance: create one consumer per independent processing loop rather than per source, create before querying historical windows to avoid a race, and ack only after processing every event from get_feed_changes. It also explains idempotent retry behavior and the 409 conflict condition, leaving little to inference.

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

All smry Product 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