Skip to main content
Glama
Sign In

Summer

by ai.gosummer.api
OverviewDiscussionsAdmin
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.

Disconnect the caller's own Slack account from Summer in this company and delete its saved token

summer_slack_account_disconnect
Destructive

Disconnect the caller's own Slack account from Summer in this company and delete its saved token. Replies set to post as the approver are then blocked for the caller, and Summer stops reading as the caller.

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>"
    },
    "name": "summer_slack_account_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesSummer company ID
idempotency_keyNoReuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantive consequences beyond the annotations: the saved token is deleted, approver-posted replies are blocked, and reading as the caller stops. That is real disclosure of what is destroyed. It doesn't address retry semantics or the idempotency_key under a destructive, idempotentHint=false operation, which would have completed the picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the action and its destructive effect are front-loaded, followed by the user-visible consequences. No filler.

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

Completeness4/5

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

For a destructive mutation with no output schema, the description conveys the essential effects and scope. Remaining gaps are minor (no explicit sibling reference, no retry/idempotency note) and mostly covered by annotations and schema.

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 100% with both parameters documented (company as Summer company ID, idempotency_key retry guidance). The description only echoes company scoping ('in this company') and adds nothing about the idempotency key, so baseline 3 applies.

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+resource ('Disconnect ... Slack account ... and delete its saved token') with explicit scope 'the caller's own' and 'in this company'. This scope wording implicitly separates it from summer_teammates_slack_disconnect, which acts on other people, so an agent can route correctly.

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?

The 'caller's own' phrasing gives clear context on when this applies (self-service disconnect) versus teammate disconnect. It does not explicitly name an alternative tool or state prerequisites, so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Summer toolsInspect
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