Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_log_timeline

Build an offline timeline from JSONL or ISO-8601-prefixed log text in an engagement, preserving raw timestamps and source lines while flagging malformed or unresolved records without inventing timezones.

Instructions

Build an offline timeline from JSONL or ISO-8601-prefixed text in an engagement. Preserves raw timestamps and source lines, reports malformed or unresolved records, and never invents a timezone.

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": {
      "engagement_id": "<engagement_id>",
      "path": "<path>"
    },
    "name": "oc_log_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
formatNoauto
timezoneNo
max_bytesNo
max_recordsNo
engagement_idYes
timestamp_fieldNotimestamp

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false), so the description adds real value by stating that raw timestamps and source lines are preserved, that malformed or unresolved records are reported rather than dropped, and that no timezone is invented. The 'offline' claim is consistent with openWorldHint=false, and nothing contradicts the non-read-only hint. It still does not describe output shape or limits, but an output schema is present to cover returns.

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?

Two sentences with no filler; the core action and accepted inputs come first, and the guarantees about raw preservation and timezone handling follow. Every clause carries distinct information.

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?

The presence of an output schema means return values need not be described, and the behavioral guarantees are well covered. However, for a 7-parameter tool with zero schema descriptions and no annotations explaining limits, the definition leaves the agent guessing about the size/count caps and the timestamp_field, which is a meaningful gap for correct invocation.

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% across 7 parameters, so the description must carry the meaning. It hints at 'format' (JSONL vs ISO-8601-prefixed text) and at the timezone parameter via 'never invents a timezone', but leaves path, engagement_id, timestamp_field, max_bytes, and max_records entirely unexplained, including no indication of defaults or truncation behavior.

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?

The description gives a specific verb and resource ('Build an offline timeline') and names the accepted input shapes ('JSONL or ISO-8601-prefixed text in an engagement'), which separates it from log-retrieval siblings like oc_audit_log or oc_browser_network_log. It stops short of explicitly naming an alternative tool, so it falls just below the top mark.

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 input-format language (use it when you have JSONL or ISO-8601-prefixed text) rather than stated as a when/when-not rule. There is no exclusion, no mention of when oc_audit_log or another log tool would be the better choice, and no prerequisites such as required engagement state.

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