Skip to main content
Glama

Get the activity log

get_activity_log

Retrieve an engagement's append-only activity log with a Markdown rendering to review audit trail and control-review actions.

Instructions

Return the append-only activity log for an engagement, plus a Markdown rendering.

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": {
      "engagementId": "<engagementId>"
    },
    "name": "get_activity_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
engagementIdYes

Output Schema

NameRequiredDescriptionDefault
countYes
eventsYes
markdownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a genuine behavioral trait: the log is append-only, and a Markdown rendering is included alongside the raw data. It stops short of stating auth requirements, ordering, or size/pagination behavior, so gaps remain.

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 tight sentence with no wasted words, front-loading the resource and the append-only trait. It is appropriately sized, though it could have used its brevity budget to add a differentiating clause.

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?

An output schema exists, so return values need not be explained, and the description covers the core purpose plus the Markdown rendering. But with no annotations and a near-twin sibling, the definition is thin on the behavioral and routing detail an agent would want.

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?

There is a single parameter at 0% schema description coverage, and the description only implies its role via 'for an engagement'. It does not explain the engagementId format or that it must reference an existing engagement, so it adds only marginal meaning.

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 (Return) and resource (append-only activity log for an engagement), which is clearly actionable. However, it does not distinguish itself from the very similar sibling get_audit_log, leaving the agent to guess which log to request.

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?

The description offers no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_audit_log or get_engagement. The agent must infer the scenario from the name alone.

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