Skip to main content
Glama

Coral intimacy conversation coach

coral_conversation_coach
Read-onlyIdempotent

Help the user find the right words to talk about intimacy, desire, boundaries, new ideas, starting things, afterwards, or different levels of desire. Returns a script, talking points, a pause line, and guidance for different partner reactions. 18+ only, non-explicit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "coral_conversation_coach"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoThe tone the user wants to use.gentle
topicNoThe conversation the user wants to have.what_i_like
situationNoA short summary of the situation in the user own words.
partnerResponseNoHow the partner has responded before, if known.unknown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond that by disclosing what the tool returns (a script, talking points, a pause line, guidance for different partner reactions) and the content policy (18+ only, non-explicit), which matters for a sensitive-topic tool. It does not mention length, tone of output, or refusal behavior, keeping it just under 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.

Conciseness4/5

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

Two sentences, front-loaded with the purpose, followed by output and scope constraints, with no filler. The long enumeration of conversation types in the first sentence is slightly list-heavy but each item maps to a real topic enum or use case.

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?

With four optional parameters, full schema coverage, and no output schema, the description carries the right burden: it explains what is produced and the content boundary. Missing is any hint about how the situation text is used or how tone changes output, but that gap is small given the schema's complete enum documentation.

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% with enums and per-field descriptions for tone, topic, situation, and partnerResponse, so the schema does the heavy lifting. The description adds only indirect meaning, notably that partnerResponse feeds the 'guidance for different partner reactions' output. That is a marginal gain over the structured data, matching the baseline 3.

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?

States a specific verb and resource: helping the user find words to talk about intimacy, with an enumerated set of conversation topics (boundaries, initiation, aftercare, desire mismatch). It also names the deliverables (script, talking points, pause line, reaction guidance), which makes the tool's output concrete. It does not explicitly distinguish itself from topical siblings like coral_desire_checkin or coral_desire_gap_plan, so it falls short of a 5.

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 enumerated conversation moments (starting things, afterwards, different levels of desire) imply when to reach for this tool, and the 18+ / non-explicit note sets a scope boundary. However, there is no explicit when-not guidance and no named alternative for adjacent needs such as a desire-mismatch plan versus a conversation script, leaving the agent to infer routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources