Skip to main content
Glama

logs

Query the append-only Structured Flight Recorder to diagnose rejected turns or gate errors, filtered by board, status, and result limit.

Instructions

Query the append-only Structured Flight Recorder (.whiteboard/logs/lattice_events.jsonl) to diagnose rejected turns or gate errors.

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

Input Schema

NameRequiredDescriptionDefault
boardNoOptional board name filter
limitNoMax entries to return (default: 20)
statusNoOptional status filter (OK, REJECTED, ERROR)
project_rootNoOptional repository root path (auto-discovered by board name or file paths if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It usefully discloses that the underlying store is append-only and identifies the exact file queried, implying a read-only inspection, but says nothing about return volume, ordering, truncation, or whether the source may be missing/rotated.

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 front-loaded sentence with the verb, resource, path, and purpose in that order, with no filler. The parenthetical path is dense but justifies its space by pinning down the data source.

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 four-parameter, optional-only read tool with no output schema, the description covers what the tool reads and why, but leaves the shape of results (entry fields, ordering, how statuses like REJECTED surface) to inference. Adequate but not fully self-sufficient for an agent diagnosing failures.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (board, limit, status, project_root) is already documented in the schema. The description adds no format, default, or interaction semantics beyond that, so the baseline 3 applies.

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) plus the exact resource and its on-disk path (.whiteboard/logs/lattice_events.jsonl), and frames the purpose as diagnosing rejected turns or gate errors. It is clearly a log-inspection tool rather than a mutation or status tool, though it does not explicitly contrast with siblings like status or turn.

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 a concrete triggering condition: use it to diagnose rejected turns or gate errors. It does not state when not to use it or name an alternative tool for adjacent needs, so it stops short of full routing guidance.

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