Conecto

Connect a support inbox

ticket_connect_inbox

Idempotent

Make one of the account's email inboxes a support inbox (open_tickets true): every new email to it opens a ticket, a reply in the same thread is added to that ticket (and reopens it), and ticket replies go out from its address in the same thread. Out-of-office replies, bounces, list mail and spam never open tickets. open_tickets false stops new tickets; answers to existing ones still arrive. Create the inbox first with email_create_inbox (email connector). Costs $0.001 per call; nothing if it fails.

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": {
      "inbox": "<inbox>"
    },
    "name": "ticket_connect_inbox"
  }
}

Input Schema

Name	Required	Description	Default
`inbox`	Yes
`open_tickets`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (idempotent, non-destructive) by describing what actually happens: new mail opens tickets, thread replies are appended and reopen tickets, outbound replies send from the inbox address. It also discloses exclusions (OOO, bounces, list mail, spam) and the cost model ($0.001 per call, free on failure).

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?

Dense but front-loaded: the primary effect comes first, then threading, then exclusions, then the flag-off case, then prerequisite and cost. Every sentence carries distinct information; nothing restates the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description covers the effects, side effects, exclusions, prerequisite, and pricing an agent needs before invoking. Nothing material is missing for a two-parameter configuration tool.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the load, and it does: the open_tickets flag is fully explained in both states (true = new tickets, false = no new tickets but replies to existing tickets still land). 'Inbox' is contextualized as one of the account's email inboxes created via email_create_inbox.

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 ('Make one of the account's email inboxes a support inbox') and immediately explains the resulting behavior. It is clearly differentiated from sibling email_list_inboxes/email_update_inbox by naming email_create_inbox as the prerequisite.

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?

Gives an explicit prerequisite ('Create the inbox first with email_create_inbox') and explains the alternative mode of the open_tickets flag. It does not explicitly contrast with email_update_inbox or ticket_update_settings, so routing among configuration siblings is left partly implicit.

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

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