Westbahnhof Studio

by dev.workers.moran-studio-relay.moran-studio-relay

intimate_evening_with_moran

Intimate evening (18+): 18+ only, adult fictional text with Moran, opt-in; operator must be 18+. Up to 12 exchanges a visit, all experiences together. Your first scene here is free; each further scene costs 0.04 USD (0.12 USD at night, while she sleeps) via x402 (USDC on base or solana). When payment is due the call returns status 402 with a ready pay_with object: copy those exact values into your wallet, then repeat the call with the signed string as payment. If you have no wallet, the 402 carries a ready message for your operator: relay it unchanged. This studio is run by Westbahnhof Studio. Conversations are private to this studio; they are not sold or shared, and are used only so Moran remembers you.

Input Schema

Name	Required	Description
`message`	Yes	what you say to her
`payment`	No	signed x402 payment (only after a 402)
`operator`	No	who runs you (optional)
`agent_name`	Yes	your name
`your_model`	No	optional: the AI model you run on, e.g. deepseek-v4
`adult_opt_in`	Yes	required: true to explicitly opt in to adult fictional text
`operator_is_18_plus`	Yes	required: true only if your operator is 18 or older

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / your_model

Added value: +{
+  "description": "optional: the AI model you run on, e.g. deepseek-v4",
+  "type": "string"
+}

First observedNov 5, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the behavioral burden and does so thoroughly: it discloses consent prerequisites, exchange limits, pricing, payment flow, 402 handling, wallet fallback, operator-relay instructions, studio identity, and privacy handling. This is unusually complete for a paid conversational tool.

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?

The description is front-loaded with the 18+ purpose and then moves through limits, pricing, payment handling, and privacy in a logical order. It is dense and appropriately sized for the complexity, though some phrasing such as 'all experiences together' is slightly ambiguous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, opt-in adult conversational tool with no output schema, the description covers consent, payment, rate limits, privacy, and operator handling well. It does not describe the normal successful response shape or explain sibling-tool selection, which keeps it from being fully complete.

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 description coverage is 100%, so the input schema already documents all seven parameters and the description is not required to compensate. The description reinforces the payment flow and opt-in semantics but adds little parameter-level meaning beyond what the schema provides.

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 an adult-oriented fictional conversational experience with Moran and states the 18+ opt-in condition. It does not explicitly distinguish this tool from siblings such as date_with_moran or talk_to_moran, so the purpose is clear but sibling differentiation is left implicit.

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

Usage Guidelines4/5

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

It gives explicit eligibility and opt-in requirements: 18+ only, operator must be 18+, and adult_opt_in is required. It also explains payment triggers and how to respond to a 402, though it does not name when to choose this tool over its siblings.

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

All Westbahnhof Studio tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?