Skip to main content
Glama

obit_list

Read-only

List tracked files with expiry dates in ascending ID order; continue paging with returned tokens and get a warning when the tracked set changes.

Instructions

Lists tracked items in ascending ID order; pass nextAfter as after and version to continue. changed warns when the full set changes; restart for a complete view. total counts this read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "obit_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPrevious nextAfter (decimal ID string); omitted starts at the beginning
limitNoResults per page; 0 uses 200; maximum 200
versionNoPrevious page version; a different current set returns changed and a warning to restart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses important behavioral traits like the ascending ID ordering and the specific state management mechanism (the 'changed' warning) which are not captured in the structured annotations or schema.

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 definition is highly efficient, front-loading the core logic (ordering and continuation) and following up with necessary state caveats without any superfluous language.

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 is responsible for listing records, the description successfully covers stateful paging, ordering, and error/warning handling, making it fully comprehensive for an AI agent.

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?

While the schema defines the parameter types, the description explains the semantics of the workflow—that 'after' and 'version' are used specifically for continuation and state tracking, adding critical functional context.

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 clearly states the action ('Lists tracked items') and the sorting logic ('ascending ID order'). Although it doesn't name the resource explicitly, the context of the sibling tools suggests it functions as the primary listing mechanism for tracked obituaries.

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 tool provides clear guidance on continuous usage by instructing the agent to pass 'nextAfter' as 'after' and using 'version' to continue the retrieval process. It also provides a crucial constraint: a restart is needed after a full set change.

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