SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_recent_tool_calls

Read-onlyIdempotent

Retrieve structured, filterable records of recent tool calls from the audit log to review session history and debug executions. Supports filtering by tool name, result count, and time window.

Instructions

Read-only. Returns recent tool call records parsed from the structured JSONL audit log (the same store the audit module writes; sassy_audit_log reads the plain-text audit.log variant). Optional max_results=50 (docstring caps at 1-1000; the code takes the newest N entries), tool_name="" filters to one tool name, since_minutes=0 means all time or only calls within the last N minutes. Output includes the call entries newest-last, the returned count, and total_in_log (all lines in the file, including skipped/malformed). Returns an empty list with a note if no audit log exists. Use for session history, debugging what ran, and usage review; for raw log text use sassy_audit_log, for keyword search use sassy_audit_search. Overlap note: sassy_audit_log covers the same recent-call history as plain text — prefer this tool when you want structured, filterable records.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tool_name`	No
`max_results`	No
`since_minutes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.15.1Sep 18, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"sassy_recent_tool_callsOutput"New value: +"sassy_recent_tool_callsDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Although annotations already declare readOnlyHint and idempotentHint, the description adds meaningful behavioral detail: it returns newest-last ordering, reports returned count plus total_in_log (including malformed lines), and returns an empty list with a note if no audit log exists. It also flags the docstring cap of 1-1000 and clarifies the code takes the newest N entries, which is valuable operational context.

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 longer than average, but it is tightly organized and every sentence adds distinct value (behavior, parameters, output shape, edge case, alternatives). It could be tightened slightly, but the density justifies its length.

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?

With an output schema present and annotations covering safety, the description fills all remaining gaps: parameter semantics, ordering, output fields, missing-log behavior, and sibling routing. Nothing needed to call the tool correctly is missing.

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

Parameters5/5

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

Schema has 0% description coverage, so the description carries the full burden and succeeds: max_results is explained as 'newest N entries' with the 1-1000 docstring cap, tool_name is described as filtering to one tool name, and since_minutes semantics are spelled out ('0 means all time or only calls within the last N minutes'). Every parameter's meaning and edge behavior is covered.

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?

States a specific verb ('Returns') and resource ('recent tool call records parsed from the structured JSONL audit log'), and explicitly differentiates from sassy_audit_log and sassy_audit_search by naming them. The read-only framing and structured/filterable positioning make the tool's role 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?

Description provides explicit when-to-use: 'Use for session history, debugging what ran, and usage review', then names alternatives for raw text and keyword search. The overlap note further tells the agent to prefer this tool for structured, filterable records, leaving no ambiguity about selection.

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

Deploy Server