Skip to main content
Glama

get_recent_activity

Retrieve recent app and window activity blocks, newest first, to review your work history. Requires screen-memory permission; set lookback minutes and block limit.

Instructions

Get recent app/window activity blocks, newest first. Requires the separate screen-memory permission.

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_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum blocks (default 50, maximum 200).
minutesNoLookback window in minutes (default 120, maximum 10080).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the permission prerequisite and the newest-first ordering, but says nothing about what an 'activity block' actually contains, whether results are paginated/capped beyond the schema's limit, or what happens when the permission is absent.

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 short sentences, zero filler, with the resource and ordering front-loaded ahead of the permission caveat. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-optional-parameter read tool this covers the essentials, and the schema handles parameter detail. However, with no output schema and no annotations, the description leaves the return shape ('activity blocks') undefined, which is the main thing an agent cannot recover elsewhere.

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 both parameters (limit, minutes) are fully documented with defaults and maxima in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, though it also does not need to.

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?

States a specific verb and resource ('Get recent app/window activity blocks') plus a meaningful ordering guarantee ('newest first'), which immediately separates it from aggregate siblings like get_app_usage. It does not name any sibling explicitly, so the differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The only guidance is a prerequisite: 'Requires the separate screen-memory permission.' There is no statement of when to choose this over get_timeline, get_app_usage, or search_screen, and no exclusions, so the agent must infer the selection rule from the resource name alone.

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