Skip to main content
Glama

get_progress_log

Retrieves the current session's progress log, with optional limit and offset, so you can review what has happened during autonomous coding runs.

Instructions

Get the full progress log for the current session. Useful for understanding what has happened.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "get_progress_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of entries to return (default: 20)
offsetNoNumber of entries to skip from the end (default: 0)
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the whole burden of behavioral disclosure. It does convey that results are scoped to the current session, but says nothing about ordering, entry volume, whether the log is read-only, or what an entry contains, and the word "full" misleads given a default page size of 20.

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 short sentences with the retrieval action front-loaded and no padding. The second sentence is close to filler, but the whole definition is tight and easy to parse.

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?

A simple read tool with a fully documented input schema and no output schema, so the bar for the description is modest. It is still thin on what the log contains and how entries are ordered, details an agent needs to interpret the result correctly.

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 all three parameters carry descriptions, including the defaults and the unusual "skip from the end" offset semantics, so the schema does the heavy lifting. The description's only added context is the current-session scoping; it says nothing further about limit or offset 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?

States a specific verb and resource (get the progress log) plus a scope (current session), which is enough to know what the tool retrieves. It does not differentiate itself from nearby siblings such as get_audit_log or get_session_stats, and the word "full" sits awkwardly against a schema that paginates by default.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Useful for understanding what has happened" is the only usage hint and it points at no concrete situation, decision, or alternative. With both get_audit_log and get_session_stats present, an agent gets no signal for choosing this log over those.

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