Skip to main content
Glama
click2mcp
by KrisTHL181

demo_help

Lists the demo CLI's top-level command groups or shows options for a specific command path; call without arguments to browse, then drill into a command.

Instructions

Show the demo CLI command tree or a command's options. Call with no argument to list the top-level command groups, then drill in.

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

Input Schema

NameRequiredDescriptionDefault
pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the interactive discover-then-drill behavior, which is the key trait here, but says nothing about unknown-path handling, whether output truncates for large trees, or that it is a pure read operation with no side effects.

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?

Two sentences, front-loaded with the purpose and followed by the usage pattern. Nothing is redundant and nothing is padding.

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 detail is unnecessary. For a single optional-parameter inspection tool the description is nearly sufficient; the only real gap is the path syntax, which matters for drilling into nested commands.

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%, so the description must compensate. It implies 'path' selects a command to fetch options for and that omitting it lists top-level groups, which covers the default-empty case. However, it never specifies the path format (space-separated, dotted, or nested), which is the main ambiguity an agent would hit.

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 ('Show') plus two concrete resources: the demo CLI command tree, or a single command's options. The distinction from siblings demo_run and hello is implicit but the resource is unambiguous enough that an agent knows this is a help/inspection tool.

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?

Gives explicit procedural guidance: call with no argument to list top-level command groups, then drill in with a path. That is a clear when/how-to-use instruction. It stops short of naming alternatives or stating exclusions (e.g. use demo_run to execute a discovered command), so it is not a full 5.

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