Struct StaticPromptHandler 

pub struct StaticPromptHandler { /* private fields */ }

Handler for a single static prompt with pre-resolved body content.

Implements pmcp::PromptHandler with required-argument validation and metadata. Each StaticPromptHandler represents ONE prompt; use StaticPromptHandler::from_configs to materialize a Vec of (name, handler) pairs from a Vec<PromptConfig> and register them via prompt_arc(name, handler) calls on the builder.

Orthogonality with skills

StaticPromptHandler is independent of [pmcp::server::skills::Skill] and bootstrap_skill_and_prompt. Downstream consumers can register both surfaces side-by-side; the toolkit makes no assumption about skill registration. The dual-surface byte-equality invariant (Phase 80 / SEP-2640 §9) applies only when a consumer wires skill + prompt for the SAME logical prompt — orthogonal to anything StaticPromptHandler does.

Implementations

impl StaticPromptHandler

pub fn new( name: impl Into<String>, description: Option<impl Into<String>>, arguments: Vec<PromptArgument>, body: impl Into<String>, ) -> Self

Create a handler for a single prompt.

body is the message text returned from handle() after required-arg validation succeeds. Pre-resolve any include_resources content into body before calling new (see StaticPromptHandler::from_configs for the canonical resolution path).

Example

use pmcp_server_toolkit::prompts::StaticPromptHandler;
let handler = StaticPromptHandler::new(
    "shipping-context",
    Some("Loads shipping policy context"),
    vec![],
    "Policies:\n- Alcohol requires adult signature.",
);

pub fn from_configs( prompts: &[PromptConfig], resources: &StaticResourceHandler, ) -> Vec<(String, Self)>

Materialize a Vec of (name, handler) pairs from prompt configs by pre-resolving each include_resources against the supplied resource handler.

Missing resources are logged at warn and skipped (matching the lifted behavior). The resulting body is the resource contents joined with \n\n---\n\n; if no resources resolve, the body is a (No resources found for prompt 'name') placeholder.

Returns the same insertion order as prompts so deterministic registration with prompt_arc(name, handler) is possible.

Trait Implementations

impl From<&ServerConfig> for StaticPromptHandler

fn from(cfg: &ServerConfig) -> Self

Build a single StaticPromptHandler from a crate::config::ServerConfig.

Returns a handler for the FIRST [[prompts]] entry, or — if none are declared — a no-op handler named "<no-prompts>" with an empty body. Multi-prompt servers should use prompt_handlers_from_config instead.

Example

use pmcp_server_toolkit::{ServerConfig, StaticPromptHandler};

let cfg = ServerConfig::default();
let _handler = StaticPromptHandler::from(&cfg);

impl PromptHandler for StaticPromptHandler

fn handle<'life0, 'async_trait>( &'life0 self, args: HashMap<String, String>, _extra: RequestHandlerExtra, ) -> Pin<Box<dyn Future<Output = Result<GetPromptResult>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

Generate a prompt with the given arguments.

fn metadata(&self) -> Option<PromptInfo>

Get prompt metadata including description and arguments schema. Returns None to use default empty metadata.