Skip to main content
Glama

wellness_webhook

Subscribe to proactive wellness alerts to reduce polling overhead. Use dry_run=true to preview sample payloads without subscribing.

Instructions

Subscribe to proactive wellness alerts to reduce polling overhead. Free. Pass dry_run=true to preview sample payloads without subscribing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsNoOptional events to subscribe: low_score, high_entropy, session_expiry
dry_runNoIf true, return sample payloads without subscribing (no public HTTPS callback required)
thresholdNoLow wellness alert threshold (1-100)
session_idYesYour active session ID
callback_urlYesHTTPS webhook callback URL (skip when dry_run=true)
cooldown_minNoMinimum minutes between repeated webhook events
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
entropy_thresholdNoOptional high-entropy threshold (0-1)
Behavior3/5

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

Annotations indicate it's a write operation (readOnlyHint=false) but do not disclose subscription lifecycle, cancellation, or error behavior. The description adds that it is 'Free' and explains dry_run behavior, but lacks details on effects of subscription, duration, or side effects.

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?

The description is two sentences, front-loaded with the core action, and contains no unnecessary words. Every sentence adds value.

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?

With 10 parameters and no output schema, the description covers the core idea but lacks details on unsubscription, error handling, event triggers, or webhook setup. It is adequate but not comprehensive for a subscription tool.

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 parameters have descriptions. The tool description emphasizes dry_run usage but does not add new semantic meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: subscribing to proactive wellness alerts to reduce polling overhead. It mentions a free nature and dry run capability. This distinguishes it from sibling tools like batch_wellness_check or get_wellness_score by emphasizing proactive alerts and polling reduction.

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 description gives usage context (reduce polling overhead) and a specific tip (dry_run for preview). However, it does not explicitly state when to avoid this tool or provide alternatives among the many sibling tools. The guidance is partial.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/delx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server