When using the generated Toolcraft CLI for an MCP proxy, it is hard to discover how to call tools because parent command listings show tool names and descriptions but not their parameters.
Example:
node todos_mcp_cli/bin/todos-mcp-cli.mjs asana
Current output lists commands such as:
list_tasks List tasks in the project grouped by section. Optionally filter to a single section by name.
details Get full details of a task including its subtasks.
But it does not expose that list_tasks accepts --section <string> and details requires --task-gid <string>. You only find that by running each individual --help, e.g.:
node todos_mcp_cli/bin/todos-mcp-cli.mjs asana details --help
Request: expose params for each tool in the parent/group help output, or provide a concise command that lists every tool with its required and optional params. For MCP proxies with many tools, having to inspect every command individually makes the CLI much harder to use.
When using the generated Toolcraft CLI for an MCP proxy, it is hard to discover how to call tools because parent command listings show tool names and descriptions but not their parameters.
Example:
Current output lists commands such as:
But it does not expose that
list_tasksaccepts--section <string>anddetailsrequires--task-gid <string>. You only find that by running each individual--help, e.g.:Request: expose params for each tool in the parent/group help output, or provide a concise command that lists every tool with its required and optional params. For MCP proxies with many tools, having to inspect every command individually makes the CLI much harder to use.