RunLite

Set where a form delivers submissions

configure_notifications

DestructiveIdempotent

Sets where a form's submissions are delivered: an email address, or WhatsApp alerts to an Indian (+91) mobile number on paid plans. A form can have one of each; calling again for the same channel replaces it. A new email address gets a confirmation link and receives nothing until it is clicked. A new WhatsApp number comes back with an optInLink: the owner opens it on that phone and sends the START message. pendingConfirmation is true until then.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "formId": "<formId>",
      "channel": "<channel>",
      "to": "<to>"
    },
    "name": "configure_notifications"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	The email address, or for "whatsapp" the mobile number, e.g. "+91 98450 22110".
`formId`	Yes
`channel`	Yes	"email", or "whatsapp" for alerts to an Indian mobile number.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations: explains that a replacement occurs per channel (consistent with idempotentHint), that the previous destination is overwritten (consistent with destructiveHint), and that new destinations are inert until confirmed via a link or START message. The pendingConfirmation and optInLink return behavior is exactly the kind of context annotations cannot convey.

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?

Four tight sentences, front-loaded with the core purpose, then replacement semantics, then the two confirmation flows. Dense and mostly free of waste, though the confirmation detail is packed into a single run-on paragraph.

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?

No output schema exists, yet the description discloses the key returned fields (optInLink, pendingConfirmation) and the gating condition for activation. It is nearly complete for a mutation tool; the only omission is any statement about formId or what happens on invalid/paid-plan-restricted requests.

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 67%; the description reinforces the 'to' and 'channel' semantics (email vs. Indian mobile, paid plan) but adds little beyond what the schema descriptions already state. formId receives no explanation in either place, which is the one real gap.

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?

Names a specific verb and resource — where a form's submissions are delivered — and enumerates the two channels (email, WhatsApp). No sibling tool touches notification routing, so the agent can distinguish it from update_form or get_form without opening a schema.

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?

Sets clear operating context: one destination per channel, repeat calls replace the existing one, and WhatsApp is limited to Indian (+91) numbers on paid plans. It doesn't name alternatives or explicitly say when not to use it, but for a tool with no true siblings the context is sufficient.

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

All RunLite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?