Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

List outreach mailboxes

outreach_mailboxes
Read-onlyIdempotent

The business's mailboxes connected for outreach: each one's mailbox_id, address, the name people see, its state (ready, daily_limit_reached, waiting_for_check, reply_check_failed, paused, paused_for_bounces, paused_for_failures, over_limit or disconnected) and what went wrong, its daily limit and what it sent in the last 24 hours, its bounce rate, and its servers. Never a password. Free.

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": "outreach_mailboxes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, but the description adds real value beyond them: the full state vocabulary, per-mailbox 24h send counts, bounce rate, and the explicit 'Never a password' data-safety guarantee plus 'Free' cost signal.

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?

A single front-loaded sentence that leads with what is returned, then the fields. It gets long in the middle with the ten-value state list, but every clause carries information.

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 input schema fields and no output schema, so the description has to describe the return shape itself — and it does, including states, limits, sends, bounce rate and servers. Pagination and ordering of the list are the only omissions.

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?

Zero parameters, so baseline is 4. The enumerated output fields compensate for the absent output schema, telling the agent what keys to expect from each record.

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

Purpose4/5

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

States a specific verb+resource (list the business's outreach-connected mailboxes) and enumerates exactly what each record contains. It's clearly distinct from outreach_connect_mailbox or outreach_update_mailbox by verb, but never says so explicitly.

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?

Usage is only implied: you call this to inspect mailbox health. There is no explicit 'use this before reconnecting a paused mailbox' or pointer to the siblings that add/update/modify mailboxes.

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

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