A
licenseA
qualityD
maintenanceAssess your business's AI automation readiness across 20 industries. Get a personalized score, specific recommendations, and time/revenue impact estimates
2
13
1
MIT
Anchored Hope Index™ | Mental Resilience Counseling
Server Details
A professional resilience and future-orientation assessment for leaders, executives, and high-perfor
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
2 toolsget_framework_metadataGet Anchored Hope Index™ Framework MetadataAInspect
Returns the scoring framework metadata: seven resilience domains, five result bands with score ranges, and the Likert scale definition. No arguments required. Read-only, no PII.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| tool | Yes | |
| domains | Yes | |
| disclaimer | Yes | |
| likertScale | Yes | |
| resultBands | Yes |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden. It clearly discloses that the call is read-only and involves no PII, which covers the main behavioral concerns for a simple metadata endpoint. It does not mention rate limits or auth, but for this low-complexity tool the disclosure is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. It front-loads the exact metadata contents and then adds the no-argument and safety constraints. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity, empty input schema, and available output schema, the description is complete. It tells the agent what is returned, that no arguments are needed, and that the operation is read-only and PII-free, which is sufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters and the schema is an empty object, so parameter semantics are intentionally trivial. The description explicitly states 'No arguments required', making the no-input expectation unambiguous and adding value beyond the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Returns'), resource ('scoring framework metadata'), and enumerates concrete contents: seven resilience domains, five result bands, and the Likert scale definition. It is clearly differentiated from the sibling run_anchored_hope_index, which is the calculation tool rather than the metadata getter.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage ('Returns the scoring framework metadata') and gives useful constraints ('No arguments required', 'Read-only, no PII'), but it does not explicitly state when to use this tool versus run_anchored_hope_index. An agent must infer that this is for definitions rather than score computation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
run_anchored_hope_indexRun Anchored Hope Index™BInspect
Educational, non-clinical structured reflection on hope and resilience. This tool provides educational information only and is not a clinical assessment or medical advice.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agency | No | Agency & Pathway Belief (1-5) | |
| meaning | No | Meaning & Purpose (1-5) | |
| futureDirection | No | Future Orientation (1-5) | |
| stressStability | No | Stress Stability (1=high drift, 5=very stable) | |
| supportConnection | No | Support & Relational Anchor (1-5) | |
| emotionalEndurance | No | Emotional Endurance (1-5) | |
| motivationStability | No | Motivation Stability (1-5) |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| tool | Yes | |
| score | Yes | |
| safety | Yes | |
| category | Yes | |
| nextSteps | Yes | |
| disclaimer | Yes | |
| resultBand | Yes | |
| totalScore | Yes | |
| domainScores | Yes | |
| resultBandLabel | Yes | |
| priorityReflectionAreas | Yes | |
| educationalInterpretation | Yes |
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations present, the description must carry the full burden of behavioral disclosure. It offers only caveats ('educational information only', 'not a clinical assessment') but does not describe what the tool does with the seven inputs, whether it produces a score, how results are presented, or any side effects. The actual behavior of 'run' remains opaque.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is only two sentences and every clause earns its place: it states the tool's purpose, frames it as educational, and includes a necessary non-clinical disclaimer. It is front-loaded with the core purpose and avoids redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The schema and output schema cover the mechanical details of parameters and results, and the description provides the essential non-clinical framing. However, it lacks any guidance on how to interpret the inputs or what happens when the tool is invoked, leaving an agent to infer the tool's core behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already describes all seven parameters with clear names and 1-5 value meanings, so the description need not repeat them. The description adds no additional parameter-level context, but this is acceptable given the 100% schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a structured reflection exercise on hope and resilience, with a specific verb ('run') and resource (Anchored Hope Index). It distinguishes the tool from the sibling by framing it as non-clinical and educational, though it could more explicitly state that it calculates a score or index.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is appropriate for educational, non-clinical reflection on hope and resilience, and explicitly cautions against using it as clinical assessment or medical advice. However, it does not state when to prefer this tool over get_framework_metadata or describe any prerequisites or contexts where it should not be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- First observed
get_framework_metadata - First observed
run_anchored_hope_index
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Related MCP Connectors
ResilienceOracle - 10 operational resilience tools: BIA, RTO/RPO, scenario testing.
8-dimension business diagnosis with Revenue Leak Score and triple-option recommendations
Transformation readiness gaps and initiative risk signals for AI agents and enterprise change leads.
Leadership-ratio benchmark, partnership ROI builder, community-launch readiness test. ELC data.
Related MCP Servers
- FlicenseAqualityCmaintenanceFour specialized AI agent skills: Integral Hermeneutics (8-lens text interpretation through any text type), Rune Wisdom (Elder Futhark divination), What-If Scenario Builder (15 foresight frameworksg), and Strategical Alignment (6-phase protocol for detecting where short-term optimization builds long-term fragility, with 9-dimension gap assessment)4-
- AlicenseNot gradedqualityBmaintenanceAI safety evaluation toolkit that scores text for care-centered alignment, detects threats like jailbreaks, and certifies AI responses against a 16-probe framework. It enables users to analyze relationship health, predict burnout risk, and ensure ethical AI interactions.18MIT
- AlicenseNot gradedqualityDmaintenanceFacilitates structured creative thinking through sequential thought processing, helping users shift from reactive problem-solving to proactive outcome creation using structural tension analysis and stage-based thinking workflows.1MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
The two tools have clearly distinct roles: one returns framework metadata and requires no arguments, while the other executes the actual structured reflection/assessment. There is no overlap or ambiguity between them.
Naming Consistency5/5
Both tools use a consistent snake_case verb_noun pattern: get_framework_metadata and run_anchored_hope_index. The names clearly differentiate metadata retrieval from running the instrument.
Tool Count5/5
Two tools is well-scoped for a dedicated single-instrument server: one to retrieve scoring/framework information and one to run the instrument itself. Each tool is necessary and earns its place.
Completeness5/5
For the stated domain of an educational hope/resilience reflection tool, the surface is complete: agents can access framework metadata and execute the reflection. No obvious lifecycle or workflow operations are missing given the intentionally limited, non-clinical scope.