Skip to main content
Glama
john-broadway

Proximo

by john-broadway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

audit_entries

Read-only

Read the PROVE ledger newest first, filter by action, target, or mutations, and return bounded rows with IDs while indicating truncation.

Instructions

READ-ONLY: read the PROVE ledger back, newest first, bounded, rows with ids; says when it truncated.

Input Schema

NameRequiredDescriptionDefault
limitNo
actionNo
targetNo
mutations_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.46.2
    • 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"
+}
  2. Addedv0.31.1

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavior beyond annotations: results are newest-first, bounded, include row ids, and the response indicates when truncation occurred.

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 a single compact sentence with no wasted words. The READ-ONLY constraint and ordering behavior are front-loaded, though the telegraphic style is slightly terse.

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-shape explanation is not required. However, with four fully undocumented parameters and no filter semantics, the description is incomplete for correct invocation of action, target, and mutations_only.

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%, so the description must explain the four parameters. It hints at bounding via 'bounded' (likely the limit), but says nothing about action, target, or mutations_only filters, leaving most parameter meaning undocumented.

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

Purpose4/5

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

States a specific verb and resource: 'read the PROVE ledger back'. It distinguishes itself from audit_verify by describing a ledger read rather than verification, though it does not explicitly name the sibling 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?

The description says the tool is READ-ONLY and reads the ledger, but gives no explicit guidance on when to use it versus audit_verify or proximo_read. There are no stated exclusions, prerequisites, or alternative-selection rules.

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