Skip to main content
Glama
thyn-ai

Algenta MCP

Official
by thyn-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_audit_logs

Read-onlyIdempotent

Retrieve your organization's audit-event log, newest first, with pagination and exact-match filters to trace who did what to which resource and the outcome.

Instructions

Query the organization's audit-event log, newest first, with pagination (defaults page 1, limit 25) and exact-match filters. Every entry records who did what to which resource with which result; an org with no events returns an honest empty page. Requires an admin API key. Use get_audit_log_artifacts for the immutable Parquet artifact copy, and filter by policy_snapshot_id, schema_snapshot_id, manifest_version, or request_hash to trace one execution. Read-only. Returns entries plus total, page, limit, and pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number; defaults to 1.
limitNoEntries per page, up to 100; defaults to 25.
actionNoKeep only events with this action, e.g. execution_policy.update.
resultNoKeep only events with this result value.
actor_emailNoKeep only events by this actor email.
request_hashNoKeep only events tied to this request hash.
resource_typeNoKeep only events against this resource type.
manifest_versionNoKeep only events tied to this runtime manifest version.
policy_snapshot_idNoKeep only events tied to this execution-policy snapshot.
schema_snapshot_idNoKeep only events tied to this schema snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.1.3
    • addedInput schema / properties / action / description
      Added value: +"Keep only events with this action, e.g. execution_policy.update."
    • addedInput schema / properties / actor_email / description
      Added value: +"Keep only events by this actor email."
    • addedInput schema / properties / limit / description
      Added value: +"Entries per page, up to 100; defaults to 25."
    • addedInput schema / properties / manifest_version / description
      Added value: +"Keep only events tied to this runtime manifest version."
    • addedInput schema / properties / page / description
      Added value: +"1-based page number; defaults to 1."
    • addedInput schema / properties / policy_snapshot_id / description
      Added value: +"Keep only events tied to this execution-policy snapshot."
    • addedInput schema / properties / request_hash / description
      Added value: +"Keep only events tied to this request hash."
    • addedInput schema / properties / resource_type / description
      Added value: +"Keep only events against this resource type."
    • addedInput schema / properties / result / description
      Added value: +"Keep only events with this result value."
    • addedInput schema / properties / schema_snapshot_id / description
      Added value: +"Keep only events tied to this schema snapshot."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only/idempotent/non-destructive annotations, the description adds behavioral details: newest-first ordering, pagination defaults, honest empty page behavior, admin key requirement, and return shape (entries, total, page, limit, pages). This substantially enriches the agent's understanding.

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?

The description is information-dense yet efficient, covering purpose, pagination, filters, empty behavior, auth, alternative tool, and return fields in a few sentences. It is front-loaded with the main purpose and avoids redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 10 parameters and no output schema, the description provides a complete picture: purpose, behavioral traits, auth prerequisite, pagination, filters, return format, and differentiation from a sibling. Nothing critical is missing for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3. The description adds value by framing certain filters (policy_snapshot_id, schema_snapshot_id, manifest_version, request_hash) as a way to trace one execution, providing context beyond the individual parameter descriptions. It also states pagination defaults which reinforce the schema, but does not fully compensate for the lack of enums or value examples.

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 the tool queries the organization's audit-event log with specific verb and resource, and distinguishes it from the sibling get_audit_log_artifacts. It also mentions pagination and exact-match filters, making the purpose unambiguous.

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

Usage Guidelines5/5

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

It explicitly directs users to get_audit_log_artifacts for the immutable Parquet artifact copy, and suggests filtering by specific fields to trace an execution. It also notes the admin API key requirement, giving clear when-to-use and alternative guidance.

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