Skip to main content
Glama
Sign In
cairn

cairn

by juw12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

recent

Read-onlyIdempotent

Retrieve journal entries from the last N days plus recently changed notes to review what happened lately in your project memory. Set the day range to match your review window.

Instructions

What happened lately: journal entries of the last N days and the most recently changed notes.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The description adds scope information the annotations cannot convey: the result is bounded to a day-window and mixes journal entries with recently modified notes. It stops short of saying anything about result size, ordering, or truncation.

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?

One sentence, front-loaded with the plain-language intent and then the precise contents via a colon list. There is no filler and nothing redundant with the schema or annotations.

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 single-parameter read tool with full annotations and no output schema, the description is adequate: it names what comes back and how far back it looks. It leaves out how much is returned and in what order, which an agent may need in order to decide between this and a targeted search.

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 carries the load, and "last N days" does explain that the single integer is a lookback window rather than a count or an offset. The default of 7 and the 1-60 bounds remain schema-only, but the core semantics of the parameter are stated.

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?

"What happened lately" plus the enumeration of journal entries over the last N days and recently changed notes gives a concrete picture of the returned resource, so the agent knows this is a recent-activity digest. It does not distinguish itself from siblings such as search, log, or list_notes, which is the only thing keeping it below 5.

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?

The framing implies a recall/summary scenario, but there is no explicit statement of when to call this instead of search, context, or list_notes. An agent must infer the selection rule from the name and the phrase "what happened lately".

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

Deploy Server

Other Tools