mooncakes.io

README

colmugx/mcp/protocol/prompt does not have a README file

#
Prompt

pub(open) trait Prompt {
  fn name(Self) -> String
  fn description(Self) -> String
  fn arguments(Self) -> Array[@colmugx/mcp/protocol/types.PromptArgument
PromptArgument]
  async fn get(Self, Json) -> Result[@colmugx/mcp/protocol/types.GetPromptResult
GetPromptResult, @colmugx/mcp/protocol/types.MCPError
MCPError]
}

Core Prompt trait following MCP protocol

name: Prompt identifier (unique)
description: Human-readable description
arguments: Array of argument definitions (@types.PromptArgument)
get: Async operation that returns prompt messages based on provided arguments

#
PromptMRTR

source

pub(open) trait PromptMRTR {
  fn name(Self) -> String
  fn description(Self) -> String
  fn arguments(Self) -> Array[@colmugx/mcp/protocol/types.PromptArgument
PromptArgument]
  async fn get(Self, Json) -> Result[PromptGetOutcome, @colmugx/mcp/protocol/types.MCPError
MCPError]
}

MRTR-aware prompt trait. Implement this instead of Prompt when a prompts/get handler needs to suspend and ask the client for input before completing. The get method receives the full get params (after _mrtr_responses has been merged on retry).

#
PromptDefinition

source

pub(all) struct PromptDefinition {
  name : String
  description : String?
  arguments : Array[@colmugx/mcp/protocol/types.PromptArgument
PromptArgument]?
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

Prompt metadata definition (for protocol responses) Describes a prompt in the prompts/list response Note: This is separate from the Prompt trait which is for implementation Note: PromptArgument, PromptMessage, GetPromptResult are defined in @types package

#
PromptGetOutcome

source

pub(all) enum PromptGetOutcome {
  Complete(@colmugx/mcp/protocol/types.GetPromptResult
GetPromptResult)
  InputRequired(input_requests~ : Map[String, @colmugx/mcp/protocol/types.InputRequestEntry
InputRequestEntry], state~ : Json)
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

The result of a prompts/get handler. Per the 2026-07-28 MRTR pattern, a handler may either complete normally (Complete) or request additional client input (InputRequired). On retry, the client resubmits with inputResponses and the echoed requestState; the handler receives those responses via _mrtr_responses in the get params.