Skip to main content
Glama

Catch up on recent chats

catch_up
Read-onlyIdempotent

Retrieve your recent AI chat activity and matching notes so you can continue previous conversations without losing context. Call this first in a new conversation.

Instructions

Call this first in every new conversation. Returns what the user did recently in any AI (the chat logs Claude, ChatGPT and others saved to Thread in the last days days, newest first) plus the notes that match topic, so you continue where they left off.

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
daysNo
topicNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral facts: results are ordered newest-first, cover logs from multiple AI providers persisted to Thread, and are supplemented with notes matched on topic. It does not discuss result limits or paging, but an output schema exists to carry that.

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?

Two sentences, front-loaded with the imperative 'call this first', then the return contents. No filler, no restatement of the title or annotations; every clause carries information an agent needs.

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?

For a two-optional-parameter read tool with full annotations and an output schema, this covers what the agent needs to decide to call it and what each parameter does. The only shortfall is undefined behavior for an empty `topic` or the effective result size, which are minor given the output schema.

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?

Schema coverage is 0%, so the description must compensate, and it does: `days` is defined as the lookback window applied to saved chats, and `topic` as the filter selecting matching notes. It does not say whether `topic` is substring, semantic, or what an empty topic means, leaving the default behavior implicit.

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?

States a specific verb and resource: returns the user's recent activity across AIs (Claude/ChatGPT chat logs saved to Thread) plus topic-matched notes. Scope is concrete (last `days` days, newest first), and framing it as the first-call default separates it from the read_note/search_chats family without ambiguity.

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?

'Call this first in every new conversation' gives an explicit trigger condition, which is stronger than most tools provide. It stops short of stating when-not to use it or naming an alternative (e.g. search_chats) for deeper lookups, so it is clear context without exclusions.

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