Skip to main content
Glama
Sign In
mcp-ia-web

mcp-ia-web

by brigsd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

run_command

Execute commands in a local terminal with persistent session state and optional timeout for long-running tasks.

Instructions

Executa um comando no terminal local (CMD/PowerShell/bash) e retorna a saída.

A sessão é persistente: o diretório de trabalho definido por change_directory é mantido entre chamadas. Use timeout (segundos) para comandos demorados; o limite máximo é controlado por MCP_MAX_TIMEOUT.

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_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYes
timeoutNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so description bears full burden. It discloses persistent session, directory state preservation, and timeout mechanism. But lacks details on error handling, output format, or security implications.

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 concise paragraphs. Front-loaded with core purpose. No unnecessary fluff, though could be slightly more compact.

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?

Given no annotations and a simple schema, the description covers key aspects like persistent session, timeout, and purpose. Output schema exists, so lack of return format detail is acceptable.

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 has no descriptions (0% coverage). Description clarifies that 'timeout' is in seconds and that the command is executed as a string, but does not elaborate on command syntax or expected format.

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 clearly states the tool executes a local terminal command and returns output. It distinguishes from sibling tools (e.g., change_directory, get_system_info) by focusing on running arbitrary commands.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides context about persistent session and directory maintenance, and explains timeout usage. However, it does not explicitly state when to use this tool versus alternatives like change_directory or list_directory.

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