Skip to main content
Glama
Sign In
server-commands-rtk

server-commands-rtk

by Ev3lynx727
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cached_commands

List all previously cached shell commands with automatic RTK token reduction and persistent caching, enabling quick recall of executed commands.

Instructions

List all cached 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": "cached_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It describes a simple read operation with no side effects, which is transparent enough. However, it does not disclose potential behaviors like pagination, data freshness, or access restrictions.

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

Conciseness5/5

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

The description is extremely concise (3 words) and front-loaded with the key action and resource. Every word earns its place with zero fluff.

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

Completeness4/5

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

For a parameter-free listing tool, the description is adequate. It tells the agent exactly what the tool does. However, given no output schema or annotations, a bit more context about the return format or scope (e.g., 'all' cached commands) would enhance completeness.

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

Parameters4/5

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

The input schema is empty and coverage is 100%, so the baseline is 4. The description implies no filtering, consistent with the schema. No additional parameter information is needed.

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

Purpose5/5

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

The description 'List all cached commands' specifies a clear verb ('List') and resource ('cached commands'), making the tool's purpose immediately obvious. It naturally distinguishes from sibling tools like 'clear_command_cache' and 'get_cache_stats'.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_cache_stats' or 'clear_command_cache'. The description gives no context about prerequisites, conditions, or exclusions.

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