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.

Change a teammate's shown name, photo or status, with the expected revision and a reason

summer_teammates_update

Change a teammate's shown name, photo or status, with the expected revision and a reason. Retiring disconnects Slack and keeps the address reserved.

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>",
      "display_name": "<display_name>",
      "avatar_url": "<avatar_url>",
      "status": "<status>",
      "reason": "<reason>"
    },
    "name": "summer_teammates_update"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes
`status`	Yes	Retired teammates keep their address forever and disconnect from Slack.
`company`	Yes
`revision`	Yes	Current revision from teammates.list.
`teammate`	Yes
`avatar_url`	Yes
`display_name`	Yes
`idempotency_key`	No	Reuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With readOnlyHint=false, destructiveHint=false, and openWorldHint=true already declared, the description adds real value by disclosing the side effect of retiring (disconnects Slack, address stays reserved) and implying optimistic-concurrency semantics via the expected revision. It stops short of describing what happens to fields not being changed or how failures/conflicts surface.

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?

Two tight sentences with zero filler, and the operation is front-loaded. The first sentence is a verbatim duplicate of the title, which is mildly redundant but harmless.

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 an 8-parameter mutation tool with no output schema, the description covers the headline behavioral effect (retirement) and the concurrency requirement, but omits that nearly all fields are required (full-replace semantics), what the reason field is for, and how errors/conflicts are reported. Annotations carry the safety profile, so the gap is moderate rather than severe.

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 only 38%, so the description must compensate. It names the core mutable fields (name, photo, status) plus revision and reason, but adds no syntax, format, or constraint detail beyond what the schema already states, and leaves company/teammate/display_name/reason semantics unexplained.

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 states a specific verb (Change) and enumerates the mutable attributes (shown name, photo, status), which cleanly separates it from siblings like summer_teammates_create, summer_teammates_names_list, and summer_teammates_mailbox_get. It does not explicitly name a sibling to differentiate against, so it lands just 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?

There is no explicit when-to-use/when-not guidance, but the note that 'Retiring disconnects Slack' implicitly routes the status=retired path away from the separate summer_teammates_slack_disconnect sibling, and 'with the expected revision' implies a read-then-write flow via teammates.list. Usage is inferable but never stated outright.

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?