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

server-commands-rtk

by Ev3lynx727
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

run_process

Execute shell commands while automatically prefixing with 'rtk' to reduce token usage by 60-90%, optimizing costs and speed.

Instructions

Run shell command. Auto-prefixed with rtk for token minimization (60-90% savings).

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": {
      "command": "<command>"
    },
    "name": "run_process"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNo
commandYes
model_usedNoModel name that executed this command (for training metadata)
timeout_msNoPer-command timeout in milliseconds (overrides server default)
clear_cacheNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.3
    • addedInput schema / properties / timeout_ms
      Added value: +{
+  "description": "Per-command timeout in milliseconds (overrides server default)",
+  "type": "number"
+}
    • removedInput schema / properties / use_raw
      Removed value: -{
-  "default": false,
-  "description": "Run raw command without RTK filtering (bypasses auto-RTK)",
-  "type": "boolean"
-}
    • removedInput schema / properties / use_rtk_filter
      Removed value: -{
-  "default": true,
-  "description": "Auto-wrap with RTK for token-minimized output (default: true)",
-  "type": "boolean"
-}
  2. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must disclose all behavioral traits. It mentions auto-prefixing but omits critical details such as whether commands are destructive, output handling, failure modes, or permission requirements. The token saving claim is useful but insufficient.

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

Conciseness3/5

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

The description is short at two sentences and front-loaded with the action. However, it sacrifices necessary detail for brevity. It is efficient but incomplete, resulting in a mediocre conciseness score.

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

Completeness1/5

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

Given 6 parameters, no output schema, and no annotations, the description is severely inadequate. It does not cover parameter meanings, return values, error states, or interaction with sibling tools. The description fails to provide a complete understanding of the tool's capabilities.

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

Parameters1/5

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

Schema description coverage is only 33% (2 of 6 parameters have descriptions). The tool description adds no parameter context, leaving most parameters (cwd, command, clear_cache, description) completely unexplained. This is a significant gap.

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 clearly states 'Run shell command' as a specific verb and resource. While it does not explicitly differentiate from sibling tools like cached_commands or execution_log, the core action is unambiguous.

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?

The description mentions auto-prefixing with rtk for token savings, which is a usage hint, but it provides no guidance on when to use this tool versus alternatives like cached_commands or resolve_uri. No context on prerequisites or best practices.

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