Skip to main content
Glama
MCP Dokploy Online
by igoruam

auditLog-all

Read-onlyIdempotent

Retrieves and filters Dokploy audit logs by date, action, user, and resource, helping you track changes and security events.

Instructions

GET /auditLog.all

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": "auditLog-all"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
actionNo
offsetNo
userIdNo
userEmailNo
resourceNameNo
resourceTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered structurally. The description adds nothing beyond that—no mention of pagination semantics, default result volume, or the fact that unreachable/offline servers may make openWorld lookups slow or incomplete.

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

Conciseness2/5

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

It is short, but that is under-specification rather than conciseness; there is no front-loaded purpose statement to trim around. The single raw endpoint token conveys no agent-usable intent.

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

Completeness1/5

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

For a nine-parameter, enum-bearing, filter-heavy query tool with no output schema, the description is completely inadequate. An agent cannot determine date formats, filtering behavior, or what a response contains.

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

Parameters1/5

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

Nine parameters exist with 0% schema description coverage, and the description provides no parameter meaning whatsoever. Critical ambiguities—from/to date format, whether action and resourceType combine as AND filters, userId vs userEmail precedence—are left entirely undocumented.

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

Purpose2/5

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

The description only restates the name as an HTTP endpoint ("GET /auditLog.all"). It implies a list operation on audit log entries, but says nothing about scope, filters, or how it differs from siblings like settings-getLogCleanupStatus or user-all.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 exclusions, and no mention of alternatives. An agent must guess whether this is a full-dump listing or a filtered query tool.

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