Skip to main content
Glama

Where things stand, and what has moved

catch_up
Read-only

Get the current state of your workspace first: lists, folders, tags, pressing tasks, recent documents, changes since your last check, and the open task you left. Use it to resume work.

Instructions

Where things stand: lists, folders, top tags, counts, pressing tasks, newest documents, a cursor; what others moved since your last catch_up; last, the open task you were on. Ask it first.

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": "catch_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoA `cursor` from a previous `catch_up`, to count from there instead: it only reads, and brings your own changes too

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.47.0
    • changedInput schema / properties / since / description
      Previous value: -"A `cursor` from a previous `catch_up`"New value: +"A `cursor` from a previous `catch_up`, to count from there instead: it only reads, and brings your own changes too"
  2. Changed1 schema field changedv1.43.2
    • changedInput schema / properties / since / description
      Previous value: -"A `cursor` a previous `catch_up` handed back. It adds what moved since to the answer; where things stand comes either way"New value: +"A `cursor` from a previous `catch_up`"
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavior by disclosing that the tool reports deltas since the last call and emits a `cursor` for chaining. It does not explain result size, the depth of history on a first call, or why idempotentHint=false despite being a read.

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?

One dense sentence with no filler, and the framing statement is front-loaded ahead of the field inventory. The telegraphic colon-and-semicolon style trades some readability for compactness, but every clause carries information.

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 no output schema, the description correctly takes on the burden of listing returned fields, and it covers the single optional parameter's purpose. For a simple read-only orientation tool with full annotation coverage, the remaining gaps (output volume, behavior of the first call) are minor.

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 coverage is 100% and the `since` parameter is fully documented in the schema, including that it is read-only and includes the caller's own changes. The description only hints at this via 'what others moved since your last `catch_up`' and repeats the cursor concept, adding little beyond the structured field.

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 enumerates exactly what the tool returns (lists, folders, top tags, counts, pressing tasks, newest documents, a cursor, recent changes by others, and the last open task), which makes the resource concrete. It lacks a clean verb-phrase framing ('retrieve an overview of...') and reads as a field dump, so it is clear but not instantly parsable.

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?

'Ask it first' is an explicit, unambiguous usage directive telling the agent to start here before other tools. It does not name any sibling or state when not to use it, so it stops short of full routing guidance.

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