Proximo

Overview Schema Source Related Servers Discussions Admin

audit_entries

Read-only

Read bounded PROVE audit ledger entries newest first, filter by action, target, or mutations only, and see whether results were truncated.

Instructions

READ-ONLY: the PROVE ledger, newest first, bounded; says when it truncated.

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_entries"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`action`	No
`target`	No
`mutations_only`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.49.1Oct 27, 2026
- removedInput schema / properties / action / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / action / default
```
Removed value: -null
```
- removedInput schema / properties / action / title
```
Removed value: -"Action"
```
- addedInput schema / properties / action / type
```
Added value: +"string"
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / mutations_only / title
```
Removed value: -"Mutations Only"
```
- removedInput schema / properties / target / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / target / default
```
Removed value: -null
```
- removedInput schema / properties / target / title
```
Removed value: -"Target"
```
- addedInput schema / properties / target / type
```
Added value: +"string"
```
- removedInput schema / title
```
Removed value: -"audit_entriesArguments"
```

Changed15 schema fields changedv0.46.2Oct 24, 2026

addedInput schema / properties / action / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / action / description

Removed value: -"Only this exact tool name, e.g. 'pve_guest_config_set'."

addedInput schema / properties / action / title
```
Added value: +"Action"
```
removedInput schema / properties / action / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

removedInput schema / properties / limit / description

Removed value: -"Newest N entries to return (default 20)."

addedInput schema / properties / limit / title
```
Added value: +"Limit"
```
removedInput schema / properties / mutations_only / description
```
Removed value: -"Only entries that changed state."
```
addedInput schema / properties / mutations_only / title
```
Added value: +"Mutations Only"
```

removedInput schema / properties / principal

Removed value: -{
-  "default": null,
-  "description": "Only entries attributed to this caller id.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedInput schema / properties / target / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / target / description

Removed value: -"Only entries against this exact target, e.g. 'vmid=100'."

addedInput schema / properties / target / title
```
Added value: +"Target"
```
removedInput schema / properties / target / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
addedInput schema / title
```
Added value: +"audit_entriesArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "audit_entriesDictOutput",
+  "type": "object"
+}

Addedv0.31.1Aug 7, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so 'READ-ONLY' earns no credit, but the description adds real behavior: results are ordered newest-first, the result set is bounded, and truncation is signaled explicitly. Ordering and truncation signaling are exactly the traits an agent needs to paginate or widen a limit.

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?

One front-loaded fragment with zero filler; the safety marker leads and ordering/truncation follow. It is arguably too terse for four undocumented parameters, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, but with zero schema description coverage across four parameters and no usage guidance, the agent is left guessing about action/target/mutations_only semantics. For a filtered ledger read, this is incomplete.

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

Parameters2/5

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

Schema description coverage is 0% for four parameters, so the description must compensate and does not. 'bounded' hints at limit and 'truncated' at the same, but action, target, and mutations_only are undocumented in both schema and description – an agent cannot tell what values action/target accept or what mutations_only filters.

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?

Names the resource ('the PROVE ledger') and ordering ('newest first') but uses no verb – the read action is only implied by 'READ-ONLY'. Sibling audit_verify is separated only implicitly (ledger reading vs. verification), so an agent must infer the distinction.

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 statement of when to use this over audit_verify or proximo_read, and no exclusions or prerequisites. The only guidance is the read-only marker, which is already in annotations.

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

Deploy Server