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.

Update voice chat settings with the expected revision

summer_messenger_voice_update

Update voice chat settings with the expected revision. Summer updates the voice assistant from these settings and the company's published help articles.

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>",
      "installation": "<installation>",
      "revision": "<revision>",
      "settings": "<settings>"
    },
    "name": "summer_messenger_voice_update"
  }
}

Input Schema

Name	Required	Description
`company`	Yes	Summer company ID
`revision`	Yes
`settings`	Yes
`environment`	Yes	Environment that owns the resource
`installation`	Yes
`idempotency_key`	No	Reuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / settings / properties / provider / description

Previous value: -"Voice service. openai (OpenAI Realtime) is the default. openai_live is OpenAI GPT-Live, which listens while it speaks and hands questions to Summer. Omit to keep the saved choice."New value: +"Voice service. openai_live (OpenAI GPT-Live) is the default: it listens while it speaks and hands questions to Summer. openai is OpenAI Realtime. Omit to keep the saved choice."

Changed3 schema fields changedOct 24, 2026

changedInput schema / properties / settings / properties / openai_voice / description

Previous value: -"OpenAI voice: one of the openai_voices listed by messenger.voice.read. Omit to keep the saved choice."New value: +"OpenAI voice for openai and openai_live: one of the openai_voices listed by messenger.voice.read. Omit to keep the saved choice."

changedInput schema / properties / settings / properties / provider / description

Previous value: -"Voice service. openai (OpenAI Realtime) is the default. Omit to keep the saved choice."New value: +"Voice service. openai (OpenAI Realtime) is the default. openai_live is OpenAI GPT-Live, which listens while it speaks and hands questions to Summer. Omit to keep the saved choice."

changedInput schema / properties / settings / properties / provider / enum

Previous value: -[
-  "openai",
-  "elevenlabs"
-]New value: +[
+  "openai",
+  "openai_live",
+  "elevenlabs"
+]

Changed3 schema fields changedOct 21, 2026

addedInput schema / properties / settings / properties / openai_voice

Added value: +{
+  "description": "OpenAI voice: one of the openai_voices listed by messenger.voice.read. Omit to keep the saved choice.",
+  "enum": [
+    "alloy",
+    "ash",
+    "ballad",
+    "coral",
+    "echo",
+    "sage",
+    "shimmer",
+    "verse",
+    "marin",
+    "cedar"
+  ],
+  "type": "string"
+}

addedInput schema / properties / settings / properties / provider

Added value: +{
+  "description": "Voice service. openai (OpenAI Realtime) is the default. Omit to keep the saved choice.",
+  "enum": [
+    "openai",
+    "elevenlabs"
+  ],
+  "type": "string"
+}

changedInput schema / properties / settings / properties / voice_id / description

Previous value: -"One of the voices listed by messenger.voice.read."New value: +"ElevenLabs voice: one of the voices listed by messenger.voice.read."

AddedOct 21, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The annotations already disclose that this is a non-read-only, non-destructive, non-idempotent update. The description adds the expected-revision concept and downstream effect on the voice assistant, but it does not explain revision conflicts, whether settings replace or merge, permission requirements, or retry behavior.

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 description is short and front-loads the main action. The second sentence is somewhat vague, but it does not add wasteful length.

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

Completeness2/5

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

For a mutation tool with required nested settings, multiple identifiers, and no output schema, the description is missing important context about revision conflicts, replacement semantics, and lifecycle behavior. Annotations cover the safety profile but not enough of the operational detail.

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

Parameters2/5

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

Schema coverage is only 50% and the schema includes a required nested settings object. The description adds some meaning to the revision parameter by calling it the expected revision, but it provides no additional guidance for the other required parameters, nested fields, or idempotency_key.

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 and resource: update voice chat settings. The expected-revision detail distinguishes it from a plain read, but it does not name the sibling voice-read tool or explain differences from other messenger update tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies that this is the update operation and that a revision is expected, but it never states when to use it versus summer_messenger_voice_read or other update tools, nor does it mention prerequisites or when not to use it.

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?