Yes or No MCP
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 |
|---|---|
| getYesOrNoD | – |
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 confusion or overlap between tools. The tool 'getYesOrNo' stands alone with a distinct purpose, making disambiguation trivial and perfect.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'getYesOrNo' follows a clear verb_noun pattern, and with no other tools to compare, there is no inconsistency.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. For a server named 'Yes or No MCP', which suggests a simple decision-making or random response service, one tool might be minimal but still functional, but it feels thin and underdeveloped compared to typical MCP servers.
Inferring the domain as providing yes/no responses, the single tool 'getYesOrNo' covers the core functionality. However, there are obvious gaps: no ability to customize responses, set parameters, or handle variations, which limits agent workflows. The surface is basic but not severely incomplete for the stated purpose.