Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Session Audit Log

get_session_log
Read-onlyIdempotent

Retrieve audit log entries for mutating operations on financial records, with filters for action, date range, and entity type.

Instructions

Retrieve mutating-operation audit log Markdown for the current connection, another audit-log label, or connection:.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum entries to return (positive integer, default 100, returns most recent)
actionNoFilter by action.
date_toNoReturn entries up to this date (YYYY-MM-DD or ISO 8601)
date_fromNoReturn entries from this date (YYYY-MM-DD or ISO 8601)
connectionNoAudit-log label, or connection:<raw connection name>; default current connection.
entity_typeNoFilter by entity type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.29.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv0.27.0
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "CREATED",
-  "UPDATED",
-  "DELETED",
-  "CONFIRMED",
-  "INVALIDATED",
-  "UPLOADED",
-  "IMPORTED",
-  "SENT",
-  "DELETE_FAILED",
-  "CONNECTION_SWITCH_INTERRUPTED",
-  "MUTATION_INDETERMINATE"
-]New value: +[
+  "CREATED",
+  "UPDATED",
+  "DELETED",
+  "DEACTIVATED",
+  "REACTIVATED",
+  "CONFIRMED",
+  "INVALIDATED",
+  "UPLOADED",
+  "IMPORTED",
+  "SENT",
+  "DELETE_FAILED",
+  "CONNECTION_SWITCH_INTERRUPTED",
+  "MUTATION_INDETERMINATE",
+  "LOG_CLEARED"
+]
  3. Addedv0.25.3
  4. Removedv0.25.2
  5. First observedv0.18.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds two useful facts beyond that: the log contains only mutating operations, and it is returned as Markdown. It still says nothing about ordering, volume, or retention, so it clears the lower annotation-adjusted bar without being rich.

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 filler; the scope constraint is placed early. It is packed slightly densely (three connection variants in one clause) but nothing is wasted.

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 no output schema, the description does at least name the return format (Markdown), which is helpful, and the schema fully documents all inputs. However, for a six-parameter audit-log reader sitting alongside list_audit_logs and clear_session_log, it lacks the disambiguation and usage context an agent needs to select it confidently.

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 six parameters are already documented with defaults, enums, and formats. The description restates the connection selector semantics ('another audit-log label, or connection:<raw name>'), which mirrors the schema entry rather than adding new meaning.

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 ('Retrieve') and resource (mutating-operation audit log Markdown) with a clear scope of which connection's log is targeted. It does not explicitly distinguish itself from siblings like list_audit_logs or clear_session_log, so the agent must infer the difference from the audit-log type alone.

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

Usage Guidelines2/5

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

No when-to-use guidance and no named alternatives, despite several plausible siblings (list_audit_logs, clear_session_log). The description only implies usage through scope (current connection vs. another label) and never says when this tool is the right choice.

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