Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Contract Testing: Get Audit Log

contract-testing_get_audit_log
Read-onlyIdempotent

Retrieve workspace audit logs to review changes, investigate pact publications, and track deployment activity. Filter by user, event type, or time range for compliance reporting.

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

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

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

TableJSON 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
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description's behavioral disclosure is supplementary. It adds context on pagination (keyset via 'from', pageNumber/pageSize) and sort defaults, which is useful and does not contradict annotations.

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?

The description is fairly concise with a clear structure: toolset, parameter list, and use cases. It avoids verbosity but repeats parameter descriptions already in the schema, which is acceptable.

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?

With 7 parameters, no output schema, and no nested objects, the description does not explain the return format (e.g., array of events, fields). It covers pagination and parameter semantics adequately but misses the response structure, which is a gap given the lack of output schema.

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 baseline is 3. The description largely rephrases schema descriptions (e.g., for 'since', 'type') with minor additions like indicating default sort order and clarifying 'keyset pagination' for 'from'. This adds limited extra meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Retrieve the audit log of events in the workspace' using a specific verb and resource. It also lists parameters and use cases, distinguishing it from sibling tools which focus on pacticipants, webhooks, etc.

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?

Four explicit use cases are provided (e.g., review recent changes, investigate publications, compliance reporting) that help an agent decide when to use this tool. However, no exclusion criteria or alternative tools are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SmartBear/smartbear-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server