Summer

This connector has been deprecated

This was a duplicate manual listing. Use Summer’s official listing, imported from the official MCP Registry. Summer’s MCP server remains active at https://api.gosummer.ai/mcp. Setup and documentation: https://gosummer.ai/docs/mcp-clients.

Check forwarding, the DNS record and sending status for one support email address now

summer_messenger_email_check

Read-onlyIdempotent

Check forwarding, the DNS record and sending status for one support email address now. Records the latest sending status; sends nothing.

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": {
      "company": "<company>",
      "environment": "<environment>",
      "channel": "<channel>"
    },
    "name": "summer_messenger_email_check"
  }
}

Input Schema

Name	Required	Description
`channel`	Yes
`company`	Yes	Summer company ID
`environment`	Yes	Environment that owns the resource

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

"Records the latest sending status; sends nothing" is genuinely useful beyond the annotations: it tells the agent no mail is dispatched and that a status snapshot is persisted. It is consistent with readOnlyHint/openWorldHint (DNS lookups are external, nothing is mutated in the user's environment) and adds information the hints alone don't convey.

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?

Two sentences, action and target front-loaded, with the no-send guarantee immediately following. Nothing is redundant with the title's phrasing in a wasteful way.

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

Completeness3/5

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

With no output schema, the agent gets no sense of what the results look like (per-check pass/fail, DNS record values, current status enum). The description covers the what and the safety profile adequately but leaves the response shape entirely implicit for a diagnostic tool.

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%; company and environment are already documented in the schema. The description's "one support email address" at least signals that the opaque, undocumented "channel" UUID identifies the mailbox being checked, but it adds no format or selection guidance beyond that implication.

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 (check) and three concrete resources (forwarding, DNS record, sending status) scoped to a single support email address. This clearly separates it from summer_messenger_email_read/update/create, though it doesn't name those siblings 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?

The word "now" implies an on-demand, point-in-time check rather than a scheduled or bulk operation, and "one support email address" indicates single-target scope. However, it never says when to prefer this over summer_verification_run or the email_read sibling, so the agent must infer the boundary.

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

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