Skip to main content
Glama

migration_listAuditEntries

Query migration audit entries from the Operaton user operation log by process definition key and date range; returns operatorId, timestamp, and operation type.

Instructions

Query the Operaton user operation log for migration audit entries. Returns operatorId, timestamp, operationType. Filters: processDefinitionKey, date range.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of entries (default: 50)
startedAfterNoFilter entries after this date-time (ISO 8601)
startedBeforeNoFilter entries before this date-time (ISO 8601)
processDefinitionKeyNoFilter by process definition key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.0
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "description": "Maximum number of entries (default: 50)",
      +  "type": "number"
      +}
    • addedInput schema / properties / processDefinitionKey
      Added value: +{
      +  "description": "Filter by process definition key",
      +  "type": "string"
      +}
    • addedInput schema / properties / startedAfter
      Added value: +{
      +  "description": "Filter entries after this date-time (ISO 8601)",
      +  "type": "string"
      +}
    • addedInput schema / properties / startedBefore
      Added value: +{
      +  "description": "Filter entries before this date-time (ISO 8601)",
      +  "type": "string"
      +}
  2. First observedv1.1.0

TDQS

A3.6/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 burden. It usefully discloses the return fields (operatorId, timestamp, operationType), which substitutes for the missing output schema, but it does not state that the call is read-only, how results are ordered, or what happens when maxResults is exceeded.

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?

Three short sentences, front-loaded with the purpose, then returns, then filters. Every clause carries information and there is no filler or redundancy.

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 simple, fully optional-parameter read query with complete schema coverage and no output schema, the description covers purpose, return shape, and filter scope adequately. It stops short of noting read-only safety, ordering, or the 50-result default that an agent would want before calling.

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 four parameters are already documented with types and formats. The description only echoes two of them ('processDefinitionKey, date range') without adding semantics such as inclusivity of boundaries or the default of maxResults. Baseline 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 ('Query the Operaton user operation log for migration audit entries') and names the returned fields, which clearly scopes it to migration-related audit entries rather than general user-operation history. It does not explicitly contrast itself with the sibling history_listUserOperations, which covers similar ground.

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?

Usage is implied by the phrase 'migration audit entries' rather than stated: there is no when-to-use, no exclusion, and no named alternative such as history_listUserOperations. An agent can infer the context but gets no explicit routing logic.

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

Deploy Server

Other Tools