Skip to main content
Glama

Mark the log

mark

Adds a labeled log line to flag a point in time and returns a cursor for retrieving entries logged afterward.

Instructions

Add a line to the log, such as before asking the user to reproduce a problem, so the entries that follow are easy to find. Returns a cursor to pass as after to get the entries logged since the mark.

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

Input Schema

NameRequiredDescriptionDefault
labelNoText for the line, like "repro 2: open popup twice". Defaults to "mark".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose that the tool writes a new line into the log and returns a cursor usable as `after`. It does not cover whether the mark line itself appears in subsequent log reads, whether cursors expire, or any permission requirements — minor gaps for a low-risk additive operation.

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 tight sentences: purpose and use case first, return value second. Nothing is wasted and the most actionable information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, non-destructive tool with no annotations and no output schema, the description covers purpose, a usage scenario, and the return value adequately. Remaining gaps (mark line visibility in log output, cursor lifetime) are small but real.

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 coverage is 100% and the single `label` parameter is fully documented in the schema, including an example and the "mark" default. The description adds no meaning beyond that, so the baseline of 3 is appropriate.

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 and resource: adding a marker line to the log, with the intent (make following entries easy to find). It clearly distinguishes itself from the retrieval siblings by explaining that it produces a cursor rather than returning entries, though it never names those siblings.

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 when-to-use scenario (before asking the user to reproduce a problem) and describes the follow-up pattern of passing the cursor as `after` to fetch entries since the mark. It does not explicitly name the retrieval tool or state when not to use this one, so it falls 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.