InputMCP
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 |
|---|---|
| collect_inputC | get image, text, or pixel art input from user. This is used to get contextual input from the user of different kinds. |
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 between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'collect_input' follows a clear verb_noun pattern.
One tool is too few for most server purposes, as it severely limits functionality and scope. It feels thin and incomplete for handling user input in a robust way.
The server's purpose appears to be collecting user input, but with only one tool, there are significant gaps. For example, no tools for validating, processing, or managing different input types, making the surface severely incomplete.