Well-Being Check
Server Details
Hosted MCP app for guided anxiety, depression, and well-being self-checks.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
Tool Definition Quality
Average 4.6/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion with other tools. Its purpose is clearly defined.
With a single tool, naming consistency is trivially maintained. The name 'mental-health-get-test' follows a clear verb_noun pattern in snake_case.
A single tool for a 'Well-Being Check' server feels thin. Although the tool can load different assessments via parameters, the overall scope would benefit from additional tools.
The tool only loads assessments into a widget, with no support for submitting answers, saving results, or viewing history. These are significant gaps for a well-being check domain.
Available Tools
1 toolmental-health-get-testMental Health TestARead-onlyIdempotentInspect
Loads one supported self-assessment into the widget by slug. Use gad7 for anxiety screening, phq9 for depression screening, and who5 for general well-being screening when the user wants to take one of those assessments.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The name or slug of the test to retrieve (e.g., 'gad7') | |
| version | No | Optional version or variant identifier |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the tool loads into a widget, implying a read operation that returns data for display. No contradictions; the desc adds contextual behavioral info beyond annotations.
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 two sentences, front-loaded with the core action and immediately provides actionable details. Every sentence adds value; no unnecessary words or repetition.
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 simplicity, clear parameter schema, and good annotations, the description covers the essential information. No output schema exists, but the output is likely a test widget; the description could hint at the return type, but this is a minor gap. Overall, it's sufficiently complete for effective use.
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 coverage is 100% with descriptions for both parameters. The description adds meaningful usage examples for the required 'name' parameter (gad7, phq9, who5), helping the agent select the correct slug. The optional 'version' parameter is not elaborated, but this 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 the tool loads a self-assessment into a widget by slug, specifying the verb 'Loads' and resource 'self-assessment'. It lists the three supported slugs and their purposes, making the purpose unambiguous.
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 explicitly provides guidance on when to use each slug: 'gad7' for anxiety, 'phq9' for depression, 'who5' for well-being. This tells the agent exactly which parameter value to choose for a given user need.
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.
Discussions
No comments yet. Be the first to start the discussion!