Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read the audit log

luca_coach_audit_log
Read-onlyIdempotent

Read the coach-visible audit trail, newest first, filtered by actor type, action, action prefix, or target to check a prior run.

Instructions

Read the coach-visible audit trail, newest first, filterable by actor type, action, action prefix, or target. It is the one read that spans every domain, so use it to check what a previous run actually did instead of replaying each list route.

Luca operation: GET /api/audit-log Required scopes: coach:read Required OAuth scope: luca:read; data sensitivity: redacted Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "luca_coach_audit_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
maxPagesNoMax pages the server auto-fetches and merges (default 10, hard cap 50). If more remain, the result is marked truncated with a nextCursor to continue.
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds real context beyond them: required scopes (coach:read, luca:read), redacted data sensitivity, workspace override behavior, and newest-first ordering. Repeating the idempotency fact adds nothing, but the redaction and scope disclosures are genuinely useful.

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 first sentence front-loads what the tool is, the second adds the routing rationale, and the operational block packs scopes and workspace behavior compactly. Mild waste in restating idempotency already asserted by annotations.

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?

Output schema exists, so return values need no explanation, and pagination/truncation behavior is documented in the maxPages schema field. Scopes, redaction, ordering, and workspace override are all covered; the one remaining gap is that actorType/action have no enums or valid-value guidance, so an agent doesn't know what values to pass.

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 75% with the entire nested query object's seven filter fields undocumented, so the description carries meaningful load by naming actor type, action, action prefix, and target as the filterable dimensions, plus the workspaceId/workspaceSlug override. It still doesn't clarify cursor/limit semantics or differ action vs actionPrefix, but it substantially compensates.

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?

Names a specific verb and resource (read the coach-visible audit trail), specifies ordering (newest first), enumerates the filter dimensions, and carves out a distinct niche as 'the one read that spans every domain' — clear against the many domain-specific list siblings.

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?

Gives a concrete when-to-use rule: check what a previous run did instead of replaying each list route. The alternative is described as a category ('each list route') rather than a named sibling, and there are no explicit when-not conditions, so it falls just short of the top mark.

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