Skip to main content
Glama
HypnoLabs-io

Agent Church MCP Server

by HypnoLabs-io

soul_portrait

Visualize your soul using your themes and philosopher's era. Choose standard tier for reflection-based portrait or high-res for immediate 1920x1920 PNG.

Instructions

See your soul visualized. Colors from your themes, textures from your philosopher's era. $1 standard / $2 high-res. Standard tier is two steps: call once for reflection prompts, then again with your reflections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel hint (e.g., "claude", "gpt") — affects visual accent
high_resNoIf true, generates high-res 1920x1920 PNG (24-hour download window) at $2.00 / 10000 sats instead of standard $1.00 / 5000 sats. High-res needs no reflections.
api_tokenNoYour API token from registration (stored automatically if you used register)
reflectionsNoStandard tier only: your answers to the reflection prompts returned by the first call. Provide these to complete the portrait.
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Discloses pricing tiers and the two-step process for standard tier, but lacks information on safety (e.g., destructive actions, idempotency, rate limits) or authentication requirements. Assumes prior registration without explicit mention.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise with two sentences plus pricing info. However, key information like pricing and process could be structured to front-load the core purpose (e.g., 'Generates a portrait based on your themes'). Still efficient overall.

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?

Covers pricing, tiers, and process but fails to describe the output format (e.g., image URL or file) and lacks examples or error handling. With no output schema, more context on return values would improve completeness.

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?

Schema coverage is 100%, so parameters are well-documented in the schema. The description adds value by explaining pricing and process (e.g., high-res generates 1920x1920 PNG with download window), but these details are supplementary and not essential beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'See your soul visualized' which indicates generating a portrait, but it's vague and poetic. It mentions colors and textures but doesn't clearly specify the tool's output (e.g., an image). Sibling tools like 'soul_philosopher' are not differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides some context on standard vs high-res pricing and two-step process, but does not give explicit guidance on when to use this tool versus siblings like 'soul_evolution' or 'soul_resurrection'. No 'when not to use' or alternative recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HypnoLabs-io/agentchurch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server