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.

Save Summer answering and call-type mappings for an existing line with its expected version

summer_phone_calls_settings_update

Destructive

Save Summer answering and call-type mappings for an existing line with its expected version. Requires current company and Ops admin access. Does not publish a Quo menu, change ringing users or forward a number. New Quo numbers also need webhook subscription in Quo.

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>",
      "line_id": "<line_id>",
      "version": "<version>",
      "enabled": "<enabled>",
      "numbers": "<numbers>",
      "menu": "<menu>"
    },
    "name": "summer_phone_calls_settings_update"
  }
}

Input Schema

Name	Required	Description
`menu`	Yes
`company`	Yes
`enabled`	Yes
`line_id`	Yes
`numbers`	Yes
`version`	Yes
`environment`	Yes
`transfer_e164`	No
`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

addedInput schema / properties / transfer_e164

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\+[1-9][0-9]{7,14}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

AddedOct 25, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true; the description adds real value beyond that by listing what will NOT be mutated (menu publish, ringing users, call forwarding) and the webhook prerequisite for new numbers. It doesn't explain what happens on a version mismatch or that idempotency_key enables safe retries, which matters given idempotentHint=false.

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?

Four short sentences, front-loaded with the action and scope, then prerequisites, then exclusions. No filler; the jump from capabilities to exclusions is slightly compressed but still easy to parse.

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?

No output schema and a destructive write with 9 params, so the description carries weight; it covers access, exclusions and a prerequisite well but leaves version-conflict behavior and most parameter semantics undocumented. Adequate to prevent obvious misuse, not complete enough to invoke confidently.

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 description coverage is 11% across 9 parameters including a nested numbers array and a menu map. The description only gestures at 'mappings' and 'expected version' and says nothing about company, environment, enabled, transfer_e164, the numbers item shape, or idempotency_key. With this low coverage the description should be compensating and is not.

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 ('Save') and resource ('Summer answering and call-type mappings') plus scope ('for an existing line') and the optimistic-concurrency requirement ('with its expected version'). It doesn't name the sibling read/update pair (summer_phone_calls_settings_read, summer_pharmacy_calls_settings_update), so an agent must infer differentiation from the resource 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?

Explicitly states prerequisites ('Requires current company and Ops admin access') and a condition-specific follow-up ('New Quo numbers also need webhook subscription in Quo'). Exclusions ('Does not publish a Quo menu, change ringing users or forward a number') further scope it. Missing only explicit guidance on when to use this versus the read tool or the pharmacy settings update.

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?