Skip to main content
Glama

Coral intimacy confidence coach

coral_confidence_practice
Read-onlyIdempotent

Give personalized, non-explicit practices for confidence in intimacy: body confidence, starting a moment of closeness, boundaries, or talking about preferences. Use when someone asks how to feel more confident or less anxious about intimacy. 18+ only.

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_confidence_practice"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoThe part of confidence the user wants to work on.body
soloNoWhether the user is doing this alone rather than with a partner.
situationNoA short summary of the situation in the user own words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful content constraints beyond that: output must be 'non-explicit' and the tool is gated to 18+, which materially shapes what the agent should expect and how it should gate use.

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?

Three short sentences, purpose front-loaded, then usage condition, then age gate; nothing is wasted. The area enumeration slightly duplicates the enum in the schema, which keeps it just short of ideal.

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?

There is no output schema, and the description never indicates what comes back (a single practice, a multi-step exercise, a list of suggestions) or whether results are personalized per call. For a coaching/generation tool with three optional parameters, that leaves a real gap in what an agent should expect.

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%: each of the three parameters has its own description, and the 'area' enum is fully enumerated. The description's area list loosely mirrors the enum but adds no format, default, or interaction guidance beyond the schema, so the baseline of 3 applies.

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: 'Give personalized, non-explicit practices for confidence in intimacy', and enumerates the covered areas (body confidence, initiation, boundaries, communication). It is clear what the tool produces, but it does not distinguish itself from siblings like coral_conversation_coach or coral_desire_checkin, which plausibly overlap.

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?

Explicitly gives a triggering condition: 'Use when someone asks how to feel more confident or less anxious about intimacy', plus a hard audience restriction of '18+ only'. It lacks any explicit when-not guidance or pointer to a sibling tool for adjacent needs (e.g. desire discrepancy or conversation scripts).

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