Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Verify a callback channel

verify_callback_channel
Idempotent

Confirms a callback channel. Pass the code for email, SMS, or WhatsApp. A webhook or Widely chat is checked again with a test message. If the code has expired or is locked, call resend_callback_channel_code.

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": {
      "channel_id": "<channel_id>"
    },
    "name": "verify_callback_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNo
channel_idYesCallback channel id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already disclose this is not read-only, is idempotent, non-destructive, and open-world. The description adds meaningful behavioral context beyond that: channel-specific verification modes and the expired/locked failure path. It does not mention permission requirements or what a successful verification returns, but with annotations covering the safety profile this is solid.

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?

Three short sentences, no waste. The core action is front-loaded, followed by channel-specific guidance and then the fallback sibling route.

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?

Given the tool's complexity, annotations, and the absence of an output schema, the description covers the essential calling behavior: code usage by channel and the fallback when a code expires or locks. It stops short of describing expected success output, but no output schema exists and the annotations already clarify the mutation/idempotency profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, with code undocumented in the schema. The description compensates by explaining that code applies to email, SMS, and WhatsApp, and implicitly that code is unnecessary for webhook/Widely channels. It adds real meaning beyond the schema, though channel_id itself is left to the schema's brief description.

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 states a specific verb and resource: it 'confirms a callback channel.' It explicitly distinguishes channel types (email/SMS/WhatsApp vs webhook/Widely chat) and names the sibling to use when the code is expired or locked, so an agent can differentiate this tool from resend_callback_channel_code without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It tells the agent exactly when a code is required (email, SMS, WhatsApp) and when verification happens without a code (webhook or Widely chat checked with a test message). It also gives an explicit alternative for the expired-or-locked case: call resend_callback_channel_code. Nothing about when to use this versus the sibling is left to inference.

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

All Widely toolsInspect
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