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.

Choose who posts approved vendor Slack replies: the Summer Ellis app, a Summer Teammate (AI employee) from its own Slack account, or the person who approves each reply, from their own connected Slack account

summer_slack_sender_update

Choose who posts approved vendor Slack replies: the Summer Ellis app, a Summer Teammate (AI employee) from its own Slack account, or the person who approves each reply, from their own connected Slack account. Uses the revision from slack.identity.read and a reason. Sends no message.

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>",
      "revision": "<revision>",
      "teammate_id": "<teammate_id>",
      "reason": "<reason>"
    },
    "name": "summer_slack_sender_update"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes
`sender`	No	Who posts. Leave out to choose from teammate_id alone. 'approver' posts as whoever approves each reply; that person needs their own Slack account connected (slack.account.read).
`company`	Yes	Summer company ID
`revision`	Yes	Current revision from slack.identity.read; 0 before the first save.
`teammate_id`	Yes	An active teammate from teammates.list when sender is 'teammate', otherwise null.
`idempotency_key`	No	Reuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedInput schema / properties / sender

Added value: +{
+  "description": "Who posts. Leave out to choose from teammate_id alone. 'approver' posts as whoever approves each reply; that person needs their own Slack account connected (slack.account.read).",
+  "enum": [
+    "summer_app",
+    "teammate",
+    "approver"
+  ],
+  "type": "string"
+}

changedInput schema / properties / teammate_id / description

Previous value: -"An active teammate from teammates.list, or null for the Summer Ellis app."New value: +"An active teammate from teammates.list when sender is 'teammate', otherwise null."

AddedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds useful behavioral context: it is a configuration update that 'sends no message' and uses a revision plus reason, which clarifies that it changes who may post rather than posting itself. It does not cover permissions or rate limits, so it is not a 5.

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?

The purpose is front-loaded in the first sentence, followed by two short sentences adding key constraints. The first sentence is long but informative rather than redundant, and there is little wasted text.

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 rich annotations, 83% schema description coverage, and no output schema, the description is mostly complete. It explains the purpose, the revision prerequisite, and that no message is sent. Minor gaps remain around permissions and what exactly happens to existing posting behavior.

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 high (83%), so the schema already documents most parameters including sender, teammate_id, and revision. The description only repeats that revision comes from slack.identity.read and mentions a reason; it adds little beyond the schema, so the baseline 3 is appropriate.

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?

The description clearly states a specific configuration action: choosing who posts approved vendor Slack replies among the Summer app, a teammate, or an approver. It does not explicitly name or differentiate from sibling tools such as summer_slack_identity_update, so it falls short of a 5.

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 implied by the sender options and the note that it uses the revision from slack.identity.read, which tells the agent this is a settings update requiring a current revision. However, it gives no explicit when-to-use guidance, exclusions, or alternatives versus sibling update tools.

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?