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.

Create, update, rotate or disable a service account

summer_service_accounts_save

Destructive

Create, update, rotate or disable a service account. A new secret goes to the trusted local helper only. Returns a local CLI command when a secret is involved.

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>",
      "account": "<account>",
      "name": "<name>",
      "environments": "<environments>",
      "scopes": "<scopes>",
      "expected_version": "<expected_version>"
    },
    "name": "summer_service_accounts_save"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`scopes`	Yes
`account`	Yes
`company`	Yes	Summer company ID
`disable`	No
`environments`	Yes
`rotate_secret`	No
`idempotency_key`	No	Reuse the same key when retrying the same change
`expected_version`	Yes	Current version you expect; 0 when the resource does not exist yet

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

B3.3/5.0

Behavior4/5

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

With destructiveHint=true already declared, the description still adds non-obvious behavior: the new secret is delivered only to a trusted local helper and a local CLI command is returned when a secret is involved. That is real context an agent cannot get from annotations. It does not mention permission requirements, concurrency/version-conflict behavior, or what a disabled account loses.

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 operation set front-loaded and no filler. It is efficiently sized, but the space saved is not spent on the mode/parameter details that would matter most.

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?

This is a destructive, multi-mode, 9-parameter mutation with no output schema and low schema coverage, yet the description omits how modes are chosen, what expected_version guards, and what happens on version mismatch. Only the secret-delivery behavior is covered; the rest of the calling contract is missing.

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 only 33% across 9 parameters, and the description clarifies none of them. It never explains expected_version semantics, environment scoping, the scopes enum values, or how idempotency_key interacts with the idempotentHint=false annotation, so it fails to compensate for the sparse schema.

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 resource (service account) and enumerates the operations (create, update, rotate, disable), which separates it cleanly from the read-only sibling summer_service_accounts_list. It does not say how a caller selects one mode over another, so the verb set is clear but the mode boundary is fuzzy.

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 only implied by the verb list; there is no guidance on when to call this versus summer_service_accounts_list, or on which parameter combination triggers create vs update vs rotate vs disable. An agent must infer mode selection from flags like disable and rotate_secret on its own.

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?