Skip to main content
Glama
click2mcp
by KrisTHL181

demo_run

Run a demo CLI command and return its output. Pass command-line arguments without the leading demo and quote arguments containing spaces.

Instructions

Run a demo CLI command and return its output. args is the command line without the leading demo; quote arguments that contain spaces. Commands that print styled text are still usable; their output is returned as-is.

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": {
      "args": "<args>"
    },
    "name": "demo_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It usefully reveals that styled output is returned verbatim and that output comes back as-is, but it says nothing about execution scope, side effects, or whether arbitrary demo subcommands can mutate state — significant gaps for a command-execution tool.

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?

Three short sentences, front-loaded with the core action, followed by parameter format then output behavior. No sentence is redundant and every one adds information an agent would otherwise have to guess.

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?

An output schema exists, so return-value details need not be explained, and the description covers the one parameter's format plus output text handling. It leaves error handling and the boundary of the "demo" command namespace unspecified, which is a modest but real gap.

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 coverage is 0% and there is a single required parameter, so the description must supply its meaning. It does explain that `args` excludes the leading `demo` and that space-containing arguments need quoting, but says nothing about allowed subcommands, flags, or malformed-input behavior.

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 ("Run a demo CLI command and return its output"), which is concrete enough that an agent knows this executes commands rather than describing them. It does not explicitly contrast with siblings like demo_help or hello, so it stops short of full differentiation.

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?

Usage is implied by the phrase "run a demo CLI command," and quoting guidance is given for arguments with spaces. There is no explicit when-to-use or when-not-to-use guidance relative to demo_help, which an agent might reasonably consider for discovering available commands.

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