apex-memory

log_query

Filter and retrieve log entries by time range, operation, page, or task ID, returning the newest matches oldest first; optionally include automatic tool events.

Instructions

Log entries filtered by time (since/until: ISO date or date-time, local time if no offset; until a date includes that day), op substring, page and task id; the newest limit matches, oldest first. include_tool adds the automatic tool events (writes, searches).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "log_query"
  }
}

Input Schema

Name	Required	Description	Default
`op`	No
`page`	No
`limit`	No
`since`	No
`until`	No
`domain`	Yes
`task_id`	No
`include_tool`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does add real value: result ordering ('newest limit matches, oldest first'), timezone resolution ('local time if no offset'), the inclusive-day rule for until, and what include_tool injects. It does not state that the operation is non-mutating, any permission/auth requirement, or expected result volume, so gaps remain for a tool with zero annotation coverage.

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 dense, front-loaded sentence: the resource and filter set come first, then ordering, then the include_tool flag. Backticks around `limit` are noise and the parenthetical timezone clause is compressed to near-telegraphic density, but no sentence is wasted.

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?

There is no output schema and no annotations, so the description is the only guidance available; it covers ordering and six of eight parameters but leaves the required domain argument and the shape/content of returned log entries undefined. Adequate to call the tool, not sufficient to predict what comes back.

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 must compensate, and it does for most of the 8 parameters: since/until accept ISO date or date-time with defined offset and day-inclusion semantics, op is a substring match, limit returns the newest N, include_tool adds automatic tool events, and page/task_id are named as filters. The required domain parameter is never explained, which is the main remaining hole.

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 (query/filter) and resource (log entries) plus the filter dimensions: time, op substring, page and task id. An agent can tell this is a read of the log store, distinct from log_append, but the description never names that sibling to make the split explicit.

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 implied by the filter vocabulary — an agent infers 'use this to find past log entries matching criteria' — but there is no explicit when-to-use/when-not guidance, no mention of log_append as the write alternative, and no note on how this relates to search or brief.

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

Deploy Server