Skip to main content
Glama

service_inspect

Read-only

Inspect VPS services and containers to check inventory, health status, recent logs, live configuration, revision history, or audit trail, helping diagnose failures and track changes.

Instructions

Inspect VPS services: inventory, deep status, logs, configuration, revisions, or audit trail.

Actions:

  • 'list': Enumerate all managed OS services and containers with state, uptime, and versions.

  • 'status': Deep health inspection of a service including exit code and failure diagnostics.

  • 'logs': Tail recent log lines (filter by 'lines', 'since', 'until', 'keyword').

  • 'config': Read live configuration files (OS) or container spec on the VPS (secrets masked).

  • 'revisions': Inspect stored historical snapshot ledger (active, previous, superseded).

  • 'audit': Query the state-changing operations audit trail for the host or service.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "service_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoService kind disambiguator
limitNoAudit log entry limit (default 50)
linesNoLog line count (default 200)
sinceNoLog window start (ISO or relative e.g. 15m)
untilNoLog window end (ISO or relative e.g. 5m)
actionYes
keywordNoCase-insensitive log keyword filter
outcomeNoAudit outcome filter
serviceNoTarget service name

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile needs no restatement; the description instead adds real context: secrets are masked in 'config' output, 'status' returns exit codes and failure diagnostics, and 'revisions' distinguishes active/previous/superseded entries. It stops short of describing pagination or output volume for 'logs'/'audit', which is a minor gap given an output schema exists.

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 scope sentence is front-loaded and the six bullets map one-to-one onto the enum values, so every line carries information an agent needs to choose an action. Formatting is scannable and free of filler, though there is mild redundancy between the header list of nouns and the bullet text.

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?

With six actions, nine parameters and only 'action' required, the description should clarify which parameters are needed or ignored per action; it only does so for 'logs'. It does cover the return content of each action, and an output schema exists, so return values need no explanation — but the action-to-parameter contract remains under-specified.

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?

Schema description coverage is 89%, so the schema already documents nearly every parameter, and the description largely repeats the log filters (lines, since, until, keyword). It does add a useful binding of those filters to the 'logs' action specifically, but says nothing about 'kind', 'limit', 'outcome', or 'service' and does not indicate which parameters are meaningful for which action.

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?

The opening sentence names a specific verb (inspect) and resource (VPS services), and the action bullets spell out six distinct read operations with their return content. An agent can map its intent to an action directly. It does not, however, explicitly separate itself from the service_control/service_manage siblings, so the read-vs-write boundary is only implied by 'Inspect' and the readOnly annotation.

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?

Each action bullet conveys what that action yields (e.g. 'status' for exit code and failure diagnostics, 'audit' for state-changing operations), which implicitly guides action selection. There is no explicit when-to-use versus a sibling tool, no statement of prerequisites, and no exclusion such as 'use service_control to change state'.

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