Skip to main content
Glama

Journal log

journal_log
Read-onlyIdempotent

Read recent agent journal entries to review completed work, outcomes, next steps, and attached audit ranges, helping you grasp context at the start of a task without scanning the full audit log.

Instructions

Read the agent journal: what was done (summary), with what outcome (outcome), what is left (next), and which range of audit entries was attached automatically to each entry. Use at the start of work to quickly grasp recent context without reading the full audit_log.

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

Input Schema

NameRequiredDescriptionDefault
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
agentNoShort consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel.
limitNo
outcomeNo
sessionNo
sinceMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value by disclosing the shape of what comes back — the summary/outcome/next fields and the auto-attached audit-entry range per record — which matters because no output schema exists. It omits ordering and pagination behavior, keeping it short of a 5.

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?

Two tight sentences, front-loaded with the resource and its returned fields before the usage instruction. The parenthetical field names make it scannable, with no filler, though the second sentence packs both the 'when' and the 'why' into one clause.

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 6-parameter, no-output-schema read tool, describing the return fields is the right instinct and largely discharges the missing output schema. However, four of six parameters remain unexplained in both schema and description, so an agent still cannot tell how to scope the read by time, session, agent, or result count.

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 only 33%: note and agent are documented, but limit, session, sinceMinutes, and outcome are bare. The description mentions 'outcome' and 'audit entries' only as returned content, never clarifying that outcome is a filter, nor explaining limit, session, or sinceMinutes. With coverage below 50% the description needed to compensate and does not.

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 ('Read') and resource ('the agent journal') and then enumerates what each entry contains (summary, outcome, next, attached audit range). It explicitly contrasts itself with the audit_log sibling, so an agent can distinguish the two without opening either schema.

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 clear timing ('at the start of work') and names the alternative it replaces ('without reading the full audit_log'). It stops short of stating when-not-to-use (e.g., for deep history or a specific entry, where audit_log or journal_entry would apply), so it is strong but not fully exhaustive.

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