Skip to main content
Glama

List Command History

list_command_history

Retrieve recent SSH command history, including completed, failed, and interrupted commands, so you can review session activity and troubleshoot issues.

Instructions

List recent command history (completed, failed, interrupted commands).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of commands to return (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2+p1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses little beyond the statuses included. It says nothing about ordering, retention window, pagination behavior, whether command output/screen state is included, or that the operation is read-only and non-destructive.

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 front-loaded sentence with no filler, and the parenthetical status list is informative rather than redundant. It is appropriately sized, though it leaves little room for the usage or behavior context an annotation-free tool needs.

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?

For a simple one-parameter read tool with no output schema, the description is minimally adequate: it identifies the resource and the states returned. It is incomplete on ordering, result volume, and whether command output is included, which matters because no annotations supply the safety profile.

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?

There is a single parameter ('limit') and schema description coverage is 100%, including its default of 50, so the schema already carries the semantics. The description adds nothing about limiting or truncation behavior, making the baseline 3 appropriate.

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 description uses a specific verb and resource ('List recent command history') and enumerates the command states covered (completed, failed, interrupted), so an agent knows exactly what is returned. It does not explicitly distinguish itself from the sibling 'list_running_commands', which keeps it from a 5.

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?

It implies this is for past commands by saying 'recent command history', but gives no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as list_running_commands for in-flight work or get_command_status for a single command.

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