Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

operation_journal

Read-only

Read bounded, metadata-only operation history for SSH server administration. Filter by server or event type to audit actions without exposing command output or credentials.

Instructions

Read bounded local metadata-only operation history; no command output or credentials are stored.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
serverNo
event_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

The description is consistent with readOnlyHint=true and destructiveHint=false, and adds real value beyond the annotations by disclosing what the data contains and excludes: metadata only, no command output, no credentials, bounded history. That tells an agent not to expect command stdout, which is a meaningful limitation not derivable from annotations.

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?

A single compact sentence with the core resource front-loaded and the storage caveat following. No filler, though phrases like 'bounded local metadata-only' are dense enough that a slightly more explicit phrasing would cost nothing.

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?

The data-scope statement covers the safety dimension well, but with no output schema and zero parameter documentation the definition leaves open what an entry looks like, ordering, and whether results are capped. For a 3-parameter tool with no return-value documentation, this is adequate but thin.

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 three parameters (limit, server, event_type). The description never explains what 'server' or 'event_type' filter on, whether event_type values are constrained, or what limits/pagination behavior 'bounded' implies. Only the vague word 'bounded' gestures at limit.

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 ... operation history', qualified as 'bounded local metadata-only'. An agent can tell this retrieves a local audit/journal of past operations rather than executing them, and the 'metadata-only' qualifier separates it from log-retrieval siblings like docker_logs.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tool is for reading past operation history. There is no explicit when-to-use statement, no mention of auditing/troubleshooting scenarios, and no pointer to any alternative (e.g., docker_logs or execute_command) for related needs.

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