Skip to main content
Glama

context_recent

Returns compact recent activity from allowlisted read-only context sources without raw logs, helping you quickly review what happened lately.

Instructions

Return compact recent activity from allowlisted read-only context sources, without raw logs.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description does carry useful behavioral weight: it declares the sources are read-only and allowlisted (safety/scope) and that output is compacted with raw logs stripped (an output-shape constraint). It stops short of stating what 'allowlisted' means operationally, whether results are time-windowed or paginated, or any error behavior.

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?

A single sentence with no filler, and the source-scoping and output-shape constraints are front-loaded. It is efficient, though its terseness is part of why other dimensions are thin rather than a model of well-budgeted detail.

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

Completeness2/5

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

For a simple one-optional-parameter tool this should be easy to complete, yet 'recent' is never defined as a time window and, with no output schema, the agent gets no sense of what fields 'compact activity' returns. The single parameter's effect is also unexplained, leaving the agent to guess at the call's semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the single 'limit' parameter, so no meaning is added beyond the schema's type and default of 10. The parameter is intuitive enough that the damage is limited, but the description does nothing to compensate for the coverage gap or clarify whether limit caps sources, events, or output size.

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?

Names a specific verb and resource ('Return compact recent activity') and constrains the source set ('allowlisted read-only context sources') while excluding an output type ('without raw logs'). That exclusion implicitly contrasts with the raw-log-reading sibling, but the description never names an alternative, so the differentiation is only partial.

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?

Usage is only implied: 'recent' and 'compact' suggest a quick orientation call rather than deep retrieval, and 'without raw logs' hints at when not to expect detail. There is no explicit statement of when to pick this over context_search or context_read_session, and no prerequisite or exclusion guidance.

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