Skip to main content
Glama
Sign In
termcp

termcp

by dbalchunas2-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_audit_log

Retrieve terminal command history from termcp with filters for tool name, timestamp, and entry count to review or debug agent activity.

Instructions

Get the audit log of commands executed. Supports filtering.

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

Input Schema

NameRequiredDescriptionDefault
toolNoFilter by tool name
countNoNumber of entries (default: 50, max: 200)
sinceNoISO timestamp - only entries after this

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral disclosure burden, yet it only states what is fetched and that filtering exists. It does not mention read-only safety, default/max result counts, pagination, ordering, or timestamp format requirements, leaving significant behavioral gaps.

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?

Two short sentences, front-loaded with the primary action. The second sentence is brief but somewhat redundant with the schema's filter parameters, so it does not fully earn its place.

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 tool is simple and the schema is fully documented, but with no annotations and no output schema, the description should provide more context about return format, pagination, or safety. It is minimally adequate but leaves clear gaps.

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 100%, so the schema already documents tool, count, and since parameters. The description adds only the generic phrase 'Supports filtering' and provides no additional syntax, format, or constraint details beyond the schema.

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: 'Get the audit log of commands executed.' This clearly distinguishes it from sibling tools like run_command or read_file, which do not retrieve historical audit records. However, it does not explicitly name or contrast itself with any alternative, so it stops short of 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 Guidelines3/5

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

The only usage signal is 'Supports filtering,' which implies the tool is for retrieving filtered audit entries. There is no explicit when-to-use, when-not-to-use, or alternative tool comparison, leaving usage largely inferred.

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