Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Contract Testing: Get Audit Log

contract-testing_get_audit_log
Read-onlyIdempotent

Retrieve and filter workspace audit log events by timestamp, user, or event type to investigate changes, pact publications, and compliance activity.

Instructions

Retrieve the audit log of events in the workspace.

Toolset: Audit

Parameters:

  • since (string): Only include events at or after this ISO 8601 timestamp

  • userUuid (string): Filter events by PactFlow user UUID

  • type (string): Filter events by type (e.g. 'pact_publication')

  • sort (string): Sort order: '+timestamp' (asc, default) or '-timestamp' (desc)

  • from (string): Start result set from this audit event UUID (keyset pagination)

  • pageNumber (number): Page number (default: 1)

  • pageSize (number): Results per page (max 100) (default: 5)

Use Cases: 1. Review recent changes to pacticipants, webhooks, or secrets 2. Investigate who published a specific pact or verification 3. Filter events by user or event type for compliance reporting 4. Track deployment recording activity across environments

Input Schema

NameRequiredDescriptionDefault
fromNoStart result set from this audit event UUID (keyset pagination)
sortNoSort order: '+timestamp' (asc, default) or '-timestamp' (desc)
typeNoFilter events by type (e.g. 'pact_publication')
sinceNoOnly include events at or after this ISO 8601 timestamp
pageSizeNoResults per page (max 100)
userUuidNoFilter events by PactFlow user UUID
pageNumberNoPage number

Output Schema

NameRequiredDescriptionDefault
pageNo
_linksNo
eventsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.43.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "AuthFailureEvent": {
+      "additionalProperties": {},
+      "properties": {
+        "payload": {
+          "$ref": "#/$defs/HttpRequestPayload"
+        },
+        "timestamp": {
+          "type": "string"
+        },
+        "tokenUuid": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        },
+        "userEmail": {
+          "type": "string"
+        },
+        "userUuid": {
+          "type": "string"
+        },
+        "username": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "CustomEvent": {
+      "additionalProperties": {},
+      "properties": {
+        "payload": {
+          "$ref": "#/$defs/CustomPayload"
+        },
+        "timestamp": {
+          "type": "string"
+        },
+        "tokenUuid": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        },
+        "userEmail": {
+          "type": "string"
+        },
+        "userUuid": {
+          "type": "string"
+        },
+        "username": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "CustomPayload": {
+      "additionalProperties": {},
+      "properties": {
+        "identityProviderId": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "EmbeddedLink": {
+      "additionalProperties": {},
+      "properties": {
+        "href": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "templated": {
+          "type": "boolean"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "HttpAuditEvent": {
+      "additionalProperties": {},
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "payload": {
+          "$ref": "#/$defs/HttpRequestPayload"
+        },
+        "response": {
+          "$ref": "#/$defs/HttpAuditResponse"
+        },
+        "timestamp": {
+          "type": "string"
+        },
+        "tokenUuid": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        },
+        "userEmail": {
+          "type": "string"
+        },
+        "userUuid": {
+          "type": "string"
+        },
+        "username": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "HttpAuditResponse": {
+      "additionalProperties": {},
+      "properties": {
+        "status": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "HttpRequestPayload": {
+      "additionalProperties": {},
+      "properties": {
+        "method": {
+          "type": "string"
+        },
+        "path": {
+          "type": "string"
+        },
+        "queryString": {
+          "type": "string"
+        },
+        "referer": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "remoteAddress": {
+          "type": "string"
+        },
+        "remoteHost": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "requestId": {
+          "type": "string"
+        },
+        "userAgent": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "_links": {
+      "additionalProperties": {},
+      "properties": {
+        "next": {
+          "additionalProperties": {},
+          "properties": {
+            "href": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "templated": {
+              "type": "boolean"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "previous": {
+          "additionalProperties": {},
+          "properties": {
+            "href": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "templated": {
+              "type": "boolean"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "self": {
+          "$ref": "#/$defs/EmbeddedLink"
+        }
+      },
+      "type": "object"
+    },
+    "events": {
+      "items": {
+        "anyOf": [
+          {
+            "$ref": "#/$defs/HttpAuditEvent"
+          },
+          {
+            "$ref": "#/$defs/AuthFailureEvent"
+          },
+          {
+            "$ref": "#/$defs/CustomEvent"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "page": {
+      "additionalProperties": {},
+      "properties": {
+        "number": {
+          "type": "number"
+        },
+        "size": {
+          "type": "number"
+        },
+        "totalElements": {
+          "type": "number"
+        },
+        "totalPages": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Addedv0.40.0
  3. Removedv0.34.0
  4. First observedv0.27.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds modest behavioral detail — default sort '+timestamp', keyset pagination via 'from', pageSize default 5 with a max of 100 — but these are restated verbatim from the schema rather than adding new operational context such as retention windows or event volume limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and the use cases earn their place, but the parameter list duplicates the schema line for line and consumes roughly half the description with zero informational gain. Structure is readable via headers, yet the redundant block is genuine bloat.

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?

This is a read-only, all-optional-parameter list tool with an output schema, so return-value description is unnecessary and safety is covered by annotations. The description covers purpose, filtering dimensions and pagination approach, leaving only minor gaps like event-type enumeration and pagination interaction.

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 the schema already documents all seven parameters including formats, defaults and bounds. The description's 'Parameters' block is a near-verbatim copy of those schema descriptions, adding no new meaning (e.g. it never explains how 'from' interacts with 'pageNumber' or what event types exist beyond the single 'pact_publication' example). 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 first sentence gives a specific verb and resource — 'Retrieve the audit log of events in the workspace' — which is unambiguous and distinguishable from siblings like contract-testing_get_team_metrics or contract-testing_list_pacticipants. It stops short of explicitly contrasting with any sibling, but no other sibling competes for the audit-log role, so an agent can select it confidently.

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

Usage Guidelines4/5

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

The four enumerated use cases (reviewing changes to pacticipants/webhooks/secrets, investigating a pact publication, compliance filtering by user or type, tracking deployments) give concrete when-to-use context. There is no explicit when-not guidance or pointer to an alternative tool, which keeps it below a 5.

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