Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Action Logs

get_action_logs

Retrieve and paginate Cutover action logs filtered by runbook, workspace, user, and date range to audit activity and track changes.

Instructions

Retrieve action logs (audit logs) from Cutover. Paginates through results up to max_pages.

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

Input Schema

NameRequiredDescriptionDefault
user_idNoOptional user ID to filter action logs by a specific user.
max_pagesNoMaximum number of pages to fetch (default 10, must be at least 1).
runbook_idNoThe runbook ID to filter action logs by.
workspace_idNoOptional workspace ID to filter action logs by workspace.
created_afterNoFilter logs after this date (ISO 8601, e.g., "2025-01-01T00:00:00Z").
created_beforeNoFilter logs before this date (ISO 8601, e.g., "2025-12-31T23:59:59Z").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 one real behavioral trait: results are paginated up to max_pages. It omits whether results are silently truncated at that cap, whether the call is read-only, and any permission requirements.

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 core purpose front-loaded and no filler. The pagination note is useful but could have been paired with a truncation caveat at no extra length cost.

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 all parameters are optional and schema-documented. However, for a six-parameter filtered query tool with no annotations, the description says nothing about default behavior when no filters are supplied or about result limits.

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 all six parameters are already documented in the schema. The description only echoes max_pages, adding no meaning beyond the structured field, 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 and resource ('Retrieve action logs') and disambiguates with the parenthetical '(audit logs)'. It does not distinguish itself from the sibling get_activities, which an agent could plausibly confuse with audit logs.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives such as get_activities. The only usage hint is the pagination note, which is about mechanics rather than tool selection.

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