Skip to main content
Glama

recent_activity

Fetch recent wiki log entries for ingests and saved answers to track what changed and review past actions.

Instructions

Recent operations from the wiki log (ingests, saved answers).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it never states that this is a read-only operation, how far back 'recent' reaches, what ordering is used, or whether results are paginated. The parenthetical examples are the only behavioral substance.

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 short, front-loaded sentence with no filler. It is efficient, though the terseness contributes to the missing scope details rather than being purely a virtue.

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-parameter read tool this is thin: the meaning of 'recent' (time window), ordering, and the limit behavior are all left undefined, and with no output schema the agent also has no idea of the shape of returned activity entries.

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 single parameter is a bare 'limit' with a default of 20. The description never mentions the limit, its units, or its maximum, so it does not compensate for the schema gap.

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?

Identifies the resource (the wiki log) and gives concrete examples of what counts as activity (ingests, saved answers), which separates it from siblings like search_wiki and list_pages. The only weakness is the absence of an explicit verb (list/read), but the noun phrase is unambiguous enough to select the tool.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of when this should be preferred over search_wiki or list_pages, and no prerequisites. The agent must infer from the words 'recent' and 'log' that this is the chronological-activity view.

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