idea-reality-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| idea_checkA | Check if a product idea already exists before building it. Use when users discuss new project ideas, ask about competition, market saturation, or whether something has been built before. Trigger phrases: "has anyone built", "does this exist", "check competition", "is this idea original", "有沒有人做過", "市場上有類似的嗎", "幫我查這個點子" |
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 with other tools, so disambiguation is perfect.
The single tool 'idea_check' follows a noun_verb pattern, and with no other tools, there is no inconsistency.
A single tool is on the lower end of what is reasonable; it is borderline for a server that might be expected to have more functionality based on its name, but it serves a narrow purpose.
The tool fully covers its stated purpose of checking if a product idea exists, with no obvious missing functionality for that specific task.