[quotemstr]

Imagine if, in addition to local MCP "servers", the MCP people had nurtured a structured CLI-based --help-equivalent consumable by LLMs and shell completion engines alike. Doing so, you unify "CLI" (trivial deployment; human accessibility) and MCP-style (structured and discoverable tool calling) in a single DWIM artifact.

But since when has this industry done the right thing informed by wisdom and hindsight?

[rsalus]

that's a pretty interesting idea. It would be nice if there was such a standard. the approach I'm taking right now: a CLI that accepts structured JSON as input, with an 'mcp' subcommand that starts a stdio server. I bundle a 'help' command with a 'describe' action for self-service guidance scoped to a particular feature/tool.

[yammosk]

There are actually a lot of great things you can to to make CLIs more helpful to agents. I use a structured help called '--capabilities' but there is a ton of JIT context you can do from the CLI as well https://keyboardsdown.com/posts/01-agent-first-clis/

[debugnik]

That structured CLI already exists: PowerShell cmdlets.

[quotemstr]

Not in any meaningful, general way on Unix systems it doesn't. Nobody uses psh outside Windows

[debugnik]

But nobody is using your hypothetical "structured CLI-based --help-equivalent consumable by LLMs and shell completion engines alike" either. In terms of mindshare, you're starting from scratch either way.

I just remembered docopt, which maybe fits the bill in a more Unixy way, but it and its ports are mostly abandoned, for various reasons.

[AshleyGrant]

Maybe they should consider using it.

[quotemstr]

Okay, but they won't. We both know that. Now what?