Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Activities

get_activities

Retrieve activities for an incident runbook to track recent actions and events, optionally filtered by date range.

Instructions

Get activities for an incident runbook to track recent actions and events.

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": {
      "runbook_id": "<runbook_id>"
    },
    "name": "get_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
runbook_idYesThe runbook ID to retrieve activities for.
created_afterNoFilter activities after this date (ISO 8601, e.g., "2025-01-01T00:00:00Z").
created_beforeNoFilter activities before this date (ISO 8601, e.g., "2025-12-31T23:59:59Z").

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It conveys that this is a retrieval operation scoped to a runbook and implies recency ordering, but it says nothing about result limits, ordering guarantees, or whether activities are permission-scoped.

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 front-loaded sentence with no wasted wording. The trailing purpose clause adds value rather than restating the name, though it is the only reason the sentence isn't maximally tight.

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?

Because an output schema exists, return values need not be explained, and the three parameters are documented. However, with zero annotations, the definition leaves behavioral gaps (ordering, volume, permissions) for a tool whose output the agent will rely on.

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%, so all three parameters are already fully documented with types, defaults, and ISO 8601 examples. The description adds no extra meaning about the created_after/created_before filters or how they interact, so 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?

The description states a specific verb and resource (get activities) scoped to an incident runbook, so the agent knows exactly what is retrieved. It does not differentiate itself from the similar-sounding sibling get_action_logs, leaving ambiguity about which activity/log source to pick.

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?

The clause 'to track recent actions and events' implies the use case (monitoring recent runbook activity), but there is no explicit when-to-use or when-not guidance and no alternative tool is named. The agent must infer that this is the choice for runbook-scoped activity history.

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