Skip to main content
Glama

Coral desire check-in

coral_desire_checkin
Read-onlyIdempotent

Explore why desire may have changed and get one personalized, consent-based intimacy exercise. Use for questions about low desire, feeling disconnected, or not knowing what changed. Non-explicit, 18+ only, and not medical advice.

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

Input Schema

NameRequiredDescriptionDefault
comfortNoHow much directness the user wants. Bold still means non-explicit.
factorsNoOptional factors the user already recognizes. Omit to let Coral infer from the situation.
partneredNoWhether the user is currently in a relationship.
situationNoA short summary of the user situation in their own words, for example "I want sex less than my partner and I feel guilty".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds meaningful guardrails: non-explicit, 18+, not medical advice, consent-based. It still does not say what happens with the returned exercise or how factors are inferred, so it is useful but not rich.

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

Conciseness5/5

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

Two sentences, front-loaded with the outcome, followed by usage triggers and then hard constraints. Every clause carries information; nothing is filler.

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 zero-required-parameter coaching tool with no output schema, the description conveys both the diagnostic framing and the single exercise deliverable. It could say slightly more about what the return looks like, but an agent has enough to select and call it.

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 all four parameters are already documented in the schema, including the comfort enum note that "bold still means non-explicit." The description reinforces tone and consent but adds no per-parameter meaning beyond the schema, making the baseline 3 correct.

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 gives a specific verb pair ("explore why desire may have changed" + "get one personalized, consent-based intimacy exercise"), which tells an agent both the investigative and generative outputs of this tool. It does not name a sibling to distinguish itself from, 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 Guidelines4/5

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

"Use for questions about low desire, feeling disconnected, or not knowing what changed" gives clear triggering contexts, which is better than most definitions. It does not state when to prefer coral_desire_gap_plan or coral_confidence_practice instead, so there is no exclusion guidance.

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