ManifestYOU
Server Details
A persistent intention layer for AI agents. Injects a soul document into model system prompts before each session. REST API + MCP server. Auth via X-API-Key header.
- 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.7/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of ambiguity. The tool's purpose is clearly described, and an agent can easily select the correct action.
The single tool name 'get_intention' follows a clear verb_noun pattern. Since there is only one tool, naming consistency is trivially maintained.
Having only one tool is on the low end of the typical range. However, for the server's narrow purpose of fetching a single type of document, the count is acceptable but feels minimal.
The server's sole purpose is to provide a soul document for AI orientation. The single operation 'get_intention' fully covers this purpose, with no missing functionality apparent from the description.
Available Tools
1 toolget_intentionAInspect
Fetch a ManifestYOU soul document — a short philosophical grounding text designed to be injected into an AI system prompt before a session begins. Call this at the start of a session to orient the model toward stillness, precision, or creative expansion before work. Paste the returned soul_document into your system prompt or before the first user message.
| Name | Required | Description | Default |
|---|---|---|---|
| session_type | No | Session orientation. analytical=precision and decision support. creative=generative and brand work. customer_service=grounded and human-facing. general=default. | general |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It indicates the tool is a fetch operation (no destructive or mutable side effects) and explains what the returned content is for. However, it does not explicitly state that the tool is read-only or safe, which would earn a 5.
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, then usage context, then specific instruction on what to do with the output. Every sentence adds essential information with no redundancy.
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 (one optional parameter, no output schema), the description covers all necessary information: what it does, when to use it, how to use the result, and parameter guidance. No gaps.
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%, so the schema already documents the parameter well. The description adds value by explaining the context for each session_type value (e.g., 'analytical=precision and decision support'), which helps agents choose the right orientation.
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 fetches a 'ManifestYOU soul document' for injecting into an AI system prompt. It uses specific verbs ('fetch', 'paste') and describes the resource and its purpose, distinguishing it as a session orientation tool.
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 says to call this at the start of a session and instructs to paste the result into the system prompt or before the first user message. This provides clear when-to-use and how-to-use guidance.
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!