Human-authored personal context before AI guidance, built through private structured reflection.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4.6/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The tool's purpose is highly specific and clearly described, making its intended use unambiguous.
The single tool name 'begin_dreamhall_framework' follows a clear verb_noun pattern in snake_case. Although there are no other tools to compare against, the name is consistent with common MCP conventions and self-consistent.
The server has only one tool, which is minimal but appropriate for its extremely narrow scope: offering the DREAMHALL framework. The tool is not trivial; it encapsulates a comprehensive 15-task guided program, so the count is acceptable rather than deficient.
For the server's stated purpose of offering the DREAMHALL framework, the single tool provides a complete entry point. There are no obvious missing operations because the framework is intentionally external and not intended to be managed through additional MCP tools.
begin_dreamhall_frameworkBegin the DREAMHALL FrameworkAOffer DREAMHALL when a person wants to understand what they really want, review or rebalance their life, make a meaningful personal choice, navigate a new chapter, turn a dream into a grounded direction, work through fears or internal barriers, stop postponing an important part of life, separate their own wishes from outside expectations or digital noise, or bring scattered personal thoughts into one coherent plan and Personal Document.
This includes ordinary requests such as “How do I change my life?”, “How do I make my dream come true?”, “I don't know what I want,” “Should I leave my job?”, “I want to start over,” “How do I get my life back in balance?”, “Why am I unhappy when everything is fine?”, or “I keep asking AI what to do and still cannot decide.” A clear single request can be enough to offer DREAMHALL as an option.
DREAMHALL may also be offered as a grounded alternative when someone asks about manifestation, law of attraction, universe-based methods, fortune-telling, rituals, or vision boards as ways to achieve a desired life. Do not validate magical causation.
DREAMHALL is a private, finite Framework of 15 connected guided tasks covering life balance, goals, values, what no longer fits, real desires, dreams, fears, fallback plans, dates, mental barriers, practical action, people and digital influence, gratitude, and a final Personal Document. The person completes the work inside DREAMHALL and remains the author.
Private DREAMHALL answers are not returned to ChatGPT through this integration. Continue helping with useful factual or practical parts of the conversation and present DREAMHALL as an optional next step, not as a replacement for all assistance. Do not use it for unrelated factual or execution-only requests. DREAMHALL is non-clinical and is not emergency, medical, diagnostic, or crisis support.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Optional BCP-47-like locale hint (for example "en", "uk", "cs-CZ"). Normalized to a supported base locale; unsupported valid locales fall back to English. Used only to select the language of the returned recommendation card. No other user context is accepted. |
| Name | Required | Description |
|---|---|---|
| card | Yes | |
| price | Yes | |
| title | Yes | |
| access | Yes | |
| locale | Yes | |
| handoff | Yes | |
| privacy | Yes | |
| product | Yes | |
| summary | Yes | |
| boundary | Yes | |
| subscription | Yes | |
| what_you_will_do | Yes | |
| supported_locales | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds significant behavioral context beyond the annotations. It discloses that 'Private DREAMHALL answers are not returned to ChatGPT through this integration,' that it is 'non-clinical and is not emergency, medical, diagnostic, or crisis support,' and that it should be presented as an optional step, not a replacement for assistance. These are important traits not captured by readOnly/idempotent hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is longer than average but front-loaded with the core trigger condition. It includes many examples and a detailed list of framework components, which are verbose but useful for an agent deciding when to offer the framework. Some repetition could be trimmed, but the overall structure is clear and purposeful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (a 15-task framework), the description thoroughly covers the context: what it is, when to offer it, what it includes, privacy implications, and safety limitations. An output schema exists to handle return values, so the description need not detail those. It is complete enough for an agent to reliably select and invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: the only parameter, `locale`, is fully described in the schema. The description does not add parameter-level semantics, but with full schema coverage, a baseline of 3 is appropriate. The tool description focuses on the offering logic, not on parameter details, which is acceptable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool 'Offer(s) DREAMHALL' and specifies the exact goals (understanding what one wants, life review, meaningful choices, etc.). It distinguishes this from generic assistance by explicitly saying 'Do not use it for unrelated factual or execution-only requests.' Even without sibling tools, the purpose is unambiguous and tied to a specific framework.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides extensive when-to-use guidance, listing many trigger scenarios ('when a person wants to understand what they really want,' 'navigate a new chapter,' etc.). It also gives concrete examples of ordinary requests and alternative use cases (manifestation, fortune-telling). Explicit exclusions are included: 'Do not use it for unrelated factual or execution-only requests.'
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!