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.

Add or remove one person who can DM this AI employee, with the expected list revision and a reason

summer_teammates_slack_dms_update

Add or remove one person who can DM this AI employee, with the expected list revision and a reason. Summer reads only DMs from people on the list. Removing someone stops Summer reading and posting in that DM. 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>",
      "teammate": "<teammate>",
      "revision": "<revision>",
      "slack_user_id": "<slack_user_id>",
      "allowed": "<allowed>",
      "reason": "<reason>"
    },
    "name": "summer_teammates_slack_dms_update"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes
`allowed`	Yes	true adds the person; false removes them.
`company`	Yes
`revision`	Yes	Current list revision from teammates.slack.dms.list (0 for an empty list).
`teammate`	Yes
`slack_user_id`	Yes	The person's Slack member ID in the company's workspace, such as U012AB3CD.
`idempotency_key`	No	Reuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Adds real context beyond annotations: removing someone stops Summer reading and posting in that DM, and the call 'sends nothing' — clarifying that no Slack message goes out. However, annotations mark it non-idempotent while the schema exposes an idempotency_key, and the description never explains retry/conflict behavior on a stale revision.

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?

Three short sentences with the action front-loaded and no filler. Slightly more could be said about the revision contract, but nothing is wasted.

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?

For a mutation with no output schema and six required params, the description omits what a stale revision produces (conflict/error) and what the call returns. The revision parameter strongly implies optimistic concurrency, yet that behavior is never spelled out.

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 57%, and the description essentially restates what the schema already documents (revision source, allowed=add/remove). The company, teammate, and reason parameters get no added meaning in the description, so it does not compensate for the coverage gap.

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 pair (add or remove) and a precisely scoped resource (one person who can DM this AI employee), plus the required revision/reason payload. It is clearly distinct from siblings like summer_teammates_slack_dms_list, which it references by name.

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?

Implies the correct workflow by requiring 'the expected list revision' from teammates.slack.dms.list, and explains the effect of the false/remove case. It does not explicitly state when to avoid this tool versus teammates_update or slack_dms_list, so exclusions are left to inference.

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?