User Steps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| user_stepsA | Present a checklist of steps to the user for manual completion. Use this tool when you need the user to perform manual actions that you cannot do programmatically, such as:
This tool automatically opens a new terminal window with an interactive checklist UI where the user can mark steps complete using keyboard controls. The tool also returns a text summary. Step types:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined as presenting checklists for manual user actions, which is distinct and self-contained.
The single tool name 'user_steps' follows a consistent snake_case pattern, and since there are no other tools to compare against, it inherently maintains consistency. No naming conflicts or mixed conventions exist.
A single tool is too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. While the tool is well-defined, a server typically benefits from multiple tools to cover related operations, making this count borderline inadequate.
The tool covers its specific domain of user interaction checklists well, including various step types like action and verification. However, as a standalone tool, it lacks broader coverage for a server that might imply more comprehensive user step management, such as creating, editing, or tracking steps over time.