Skip to main content
Glama
inboxd
by 47star

get_recent_records

Browse records in reverse chronological order without a search query, optionally scoped to one source. Returns previews and IDs for follow-up retrieval.

Instructions

Browse content newest first without a search query, optionally scoped to one source.

Returns bounded previews and IDs for get_message/get_conversation. Excludes deleted records and Slack metadata entities. before/after are inclusive ISO 8601 timestamps with timezone. Calendar uses occurrence start, mail uses sent time, Notes/Reminders use creation time. Redmine uses issue update time and exposes work_item fields in previews. Future calendar entries are included unless before is supplied. For recently collected or modified data use get_changes instead. Continue with next_cursor and unchanged filters. For a specific channel or DM, pass conversation_id from list_slack_conversations.

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

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
beforeNo
cursorNo
sourceNo
conversation_idNo

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?

No annotations exist, so the description carries the full burden, and it delivers: excludes deleted records and Slack metadata entities, discloses per-source timestamp semantics (occurrence start, sent time, creation time, issue update time), and notes future calendar entries appear unless before is set. It stops short of stating read-only behavior explicitly, auth requirements, or limits on result volume.

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?

Lead sentence front-loads the core purpose, followed by tight sentences each carrying distinct information (return shape, exclusions, timestamp semantics, alternative, pagination). The per-source timestamp sentences are dense but each earns its place by preventing wrong date-range assumptions.

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 and no annotations, the description covers return shape, filtering, exclusions, pagination, and cross-tool handoffs well. The main remaining gap is that valid values for 'source' are never pointed to (e.g., via list_sources), leaving an agent to guess the enum-less string.

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 description coverage is 0%, so the description must compensate, and it does for five of six parameters: inclusive ISO 8601 with timezone for before/after, source scoping, conversation_id provenance, and cursor continuation with unchanged filters. Only 'limit' is left unaddressed, relying on the schema's default and 1-100 bounds.

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 ('browse content newest first without a search query') plus the scoping option, and immediately distinguishes itself from the search-style siblings. Return shape ('bounded previews and IDs for get_message/get_conversation') clarifies what the browse actually yields.

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?

Gives explicit routing: use get_changes for recently collected/modified data, and use list_slack_conversations to obtain conversation_id first. The 'without a search query' framing implicitly excludes search_messages, though it never names that sibling as an alternative.

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