Skip to main content
Glama
Sign In

Send4

by ai.send4
OverviewDiscussionsAdmin

Numbers and mailboxes

list_channels
Read-onlyIdempotent

Lists the workspace's sending numbers, mailboxes and web chat widgets: id, type, the number or address, whether it is active, and whether a campaign may send from it (campaign_sender), and why not. A connected mailbox also has connection: whether it works, and what is wrong if not. get_mailbox_setup says how to add a mailbox.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_inactiveNoInclude switched-off numbers. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new context about what the data means — `campaign_sender` and why it may be false, plus `connection` status for mailboxes. It does not discuss result size or empty-result behavior, but for a read-only listing that is minor.

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?

Front-loaded with the resource and its returned fields, then the two clarifying notes about connection status and the related tool. The four-line sentence is dense but each clause carries information; slight compression could improve skimmability.

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?

With no output schema, the description's enumeration of returned fields (including the reason a channel cannot send) is exactly the context an agent needs, and the get_mailbox_setup pointer closes the follow-up path. Only minor gaps remain, such as pagination or ordering of results.

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 description coverage is 100% and the single parameter's meaning and default are fully documented in the schema. The description only implies filtering via 'whether it is active' and adds no syntax or behavioral detail about include_inactive, so the baseline 3 applies.

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?

States a specific verb and resource ('Lists the workspace's sending numbers, mailboxes and web chat widgets') and enumerates the returned attributes (id, type, number/address, active, campaign_sender). It also explicitly separates itself from get_mailbox_setup, which handles adding a mailbox, so an agent can pick it without opening the 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?

The description makes the use case clear (inventory of sendable channels and their send-eligibility) and routes the adjacent action to get_mailbox_setup. It does not spell out when-not-to-use or name list_* siblings for other resources, so it stops short of full alternative routing.

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

All Send4 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