Skip to main content
Glama
l33tdawg

(S)AGE

by l33tdawg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

sage_backlog

Retrieve open tasks assigned to your agent ID across domains, with pagination to review priorities and track discussed but unfinished work. Unassigned tasks are excluded.

Instructions

View open tasks explicitly assigned to this agent ID across domains. Unassigned and other agents' work is never returned. Use this to see what's been discussed but not yet done, review priorities, and avoid losing track of ideas across sessions. This listing is PAGED: one call is never the whole board. Read total_open, returned, has_more and next_offset, and page with offset until has_more is false before claiming you have seen every task. scan_capped means the node stopped scanning at its bound, so narrow by domain or provider to see the remainder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoTasks per page (default 25, maximum 100).
domainNoFilter by domain (omit for all domains)
offsetNoZero-based offset into the same stable order (created_at DESC, then memory_id). Pass the previous page's next_offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv11.20.2
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Tasks per page (default 25, maximum 100).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Zero-based offset into the same stable order (created_at DESC, then memory_id). Pass the previous page's next_offset.",
+  "minimum": 0,
+  "type": "integer"
+}
  2. Addedv11.13.9
  3. Removedv11.13.8
  4. Addedv11.13.0
  5. Removedv11.9.2
  6. Addedv8.1.0
  7. Removedv8.0.0
  8. Addedv7.6.1
  9. Removedv7.5.9
  10. First observedv4.5.2

TDQS

A4.6/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 thoroughly: it calls out pagination, lists the response fields to inspect ('total_open', 'returned', 'has_more', 'next_offset'), instructs to page until has_more is false, and explains the scan_capped boundary. It also states the exclusion guarantee for unassigned tasks.

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?

The description is front-loaded with purpose and scope before moving into pagination mechanics. It is longer than average, but the added sentences carry necessary behavioral warnings (paging, scan_capped) rather than padding, so each sentence earns its place.

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?

Despite having no output schema, the description names the critical response fields and gives a complete algorithm for consuming the paginated list. An agent has everything needed to call it correctly and to know when it has seen all tasks, including a mitigation for scan_capped.

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 input schema already documents all three parameters (100% coverage), so the baseline is 3. The description adds value by tying 'offset' to 'next_offset' pagination behavior and advising users to 'narrow by domain or provider' when scan_capped is true, which goes beyond the bare schema definitions.

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 first line states a specific action and resource: 'View open tasks explicitly assigned to this agent ID across domains.' It also carves out its scope with 'Unassigned and other agents' work is never returned,' making the tool's boundary clear without needing to open 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 Guidelines4/5

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

The description gives concrete use cases ('see what's been discussed but not yet done, review priorities, and avoid losing track of ideas across sessions') and warns about pagination. It does not explicitly name sibling alternatives or say when not to use this tool, but the intended context is clear.

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