Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

audit_recent

Read-only

Inspect recent local operations and approval decisions to review what happened and verify command approvals.

Instructions

Inspect recent local operations and approval decisions.

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": "audit_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoRecent events 1..80

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is fully covered by structured data. The description adds only the content domain (local operations and approval decisions) and says nothing about retention window, ordering, how far back "recent" reaches, or whether the log is paginated — context annotations cannot supply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no wasted words and the resource front-loaded, which is good. It is concise to the point of under-specification: the single sentence leaves the most useful facts (what an event is, what the return looks like) unstated rather than being tight because the content is complete.

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?

A one-parameter read-only tool with full schema coverage and annotations is a low bar, and the description clears it minimally. Because there is no output schema, the description should at least signal the shape of a returned event record and the ordering, and it does not.

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?

There is a single optional parameter, and the schema documents it fully ("Recent events 1..80", default 30), so coverage is 100%. The description adds no meaning beyond that — it doesn't explain that count caps how far back the audit trail is read — which matches the baseline-3 expectation when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs the verb "Inspect" with a resource, "recent local operations and approval decisions," so the general domain is clear. However, "local operations" is undefined — an agent can't tell whether that means file edits, git actions, or tool invocations, and nothing distinguishes this from the many sibling inspection tools such as list_snapshots, checkpoint_list, or git_log.

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?

There is no when-to-use guidance, no stated prerequisites, and no mention of alternatives. The only implicit signal is the word "recent" plus the count default, which hints at a default window but never says when an agent should prefer this over list_snapshots or checkpoint_list.

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