Skip to main content
Glama
MarkAC007

mcp-server-scf

by MarkAC007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

scf_get_audit_log

Read-only

Retrieve field-level changes from an organization's append-only audit trail, showing actor, source, and before/after values. Filter by entity, control, action, actor, source, date, or text.

Instructions

Query one organization's append-only audit trail (read — viewer role): field-level changes with actor, source and before/after values. Filter by entity, control, action, actor, source, date or text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (1–200, default 50)
actionNoFilter by action: create, update or delete
offsetNoPagination offset — number of results to skip (default 0)
org_idYesOrganization UUID — obtain from scf_list_organizations
scf_idNoFilter by SCF control ID in DOMAIN-NN format
date_toNoInclude changes at or before this ISO-8601 timestamp (YYYY-MM-DDTHH:MM:SSZ)
actor_idNoFilter by actor user UUID — platform alias of changed_by_user_id
date_fromNoInclude changes at or after this ISO-8601 timestamp (YYYY-MM-DDTHH:MM:SSZ)
entity_idNoFilter by the changed entity's UUID
request_idNoFilter by request correlation ID — groups every change one API call made
entity_typeNoFilter by exact entity type as written in the log, e.g. scoped_control, evidence_file, audit_engagement, vendor — unsure of the spelling? use search_text
search_textNoCase-insensitive search across entity_type, field_name, old_value and new_value
action_sourceNoFilter by origin of the change: ui, api_key, mcp or system
changed_by_user_idNoFilter by the user who made the change — obtain from scf_list_members

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv3.4.2
    • addedInput schema / properties / action
      Added value: +{
+  "description": "Filter by action: create, update or delete",
+  "enum": [
+    "create",
+    "update",
+    "delete"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / action_source
      Added value: +{
+  "description": "Filter by origin of the change: ui, api_key, mcp or system",
+  "enum": [
+    "ui",
+    "api_key",
+    "mcp",
+    "system"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / actor_id
      Added value: +{
+  "description": "Filter by actor user UUID — platform alias of changed_by_user_id",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
    • addedInput schema / properties / changed_by_user_id
      Added value: +{
+  "description": "Filter by the user who made the change — obtain from scf_list_members",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
    • addedInput schema / properties / date_from
      Added value: +{
+  "description": "Include changes at or after this ISO-8601 timestamp (YYYY-MM-DDTHH:MM:SSZ)",
+  "type": "string"
+}
    • addedInput schema / properties / date_to
      Added value: +{
+  "description": "Include changes at or before this ISO-8601 timestamp (YYYY-MM-DDTHH:MM:SSZ)",
+  "type": "string"
+}
    • addedInput schema / properties / entity_id
      Added value: +{
+  "description": "Filter by the changed entity's UUID",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
    • addedInput schema / properties / entity_type
      Added value: +{
+  "description": "Filter by exact entity type as written in the log, e.g. scoped_control, evidence_file, audit_engagement, vendor — unsure of the spelling? use search_text",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Page size (1–100, default 50)"New value: +"Page size (1–200, default 50)"
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +200
    • addedInput schema / properties / request_id
      Added value: +{
+  "description": "Filter by request correlation ID — groups every change one API call made",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
    • addedInput schema / properties / scf_id
      Added value: +{
+  "description": "Filter by SCF control ID in DOMAIN-NN format",
+  "type": "string"
+}
    • addedInput schema / properties / search_text
      Added value: +{
+  "description": "Case-insensitive search across entity_type, field_name, old_value and new_value",
+  "type": "string"
+}
  2. First observedv1.7.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's 'read' is consistent. It adds valuable behavioral context beyond the annotation: the trail is append-only, requires viewer role, and returns field-level changes with actor, source, and before/after values. No contradiction with annotations.

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?

Two sentences with no filler. The first sentence states the core purpose and return content; the second enumerates the filter dimensions. All essential information is front-loaded.

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?

There is no output schema, but the description partially compensates by naming the returned content (field-level changes with actor, source, and before/after values). The schema fully documents all 14 parameters, and the description covers the filter dimensions. It could add ordering or pagination behavior, but nothing critical is missing for selecting and invoking the tool.

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 description coverage is 100%, so the baseline is 3. The description adds value by grouping the 14 parameters into meaningful filter categories ('entity, control, action, actor, source, date or text'), which helps an agent map intent to the right parameter without reading every schema entry.

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 names a specific verb ('Query'), a specific resource ('one organization's append-only audit trail'), and the exact content ('field-level changes with actor, source and before/after values'). It also states the access level ('read — viewer role'), making it clearly distinguishable from the many mutation tools in the sibling list.

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 description makes the tool's context clear: it is for reading audit log entries for a single organization, with filtering by entity, control, action, actor, source, date, or text. It does not explicitly name alternatives or state when not to use it, but the purpose is specific enough that an agent can infer when this is the right tool.

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