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.

List the people who can DM this AI employee in Slack, with the list revision, plus `people`: names and member IDs Summer has seen in the selected channels, to choose from

summer_teammates_slack_dms_list
Read-onlyIdempotent

List the people who can DM this AI employee in Slack, with the list revision, plus people: names and member IDs Summer has seen in the selected channels, to choose from. Each DM from one of them opens an Ops case; a person approves the exact reply before the AI employee posts it. Needs a company owner or administrator.

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

Input Schema

NameRequiredDescriptionDefault
companyYes
teammateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already mark it read-only, idempotent, open-world, and non-destructive; the description adds that each DM opens an Ops case and that a human approves replies, plus the admin requirement. It also discloses the response contains a list revision and people names/member IDs, which is useful output context without an output schema.

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 sentences, front-loaded with the list action and return contents. The Ops-case/human-approval sentence adds behavioral context, and the admin sentence is brief; there is some title overlap but no serious waste.

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?

The description covers return contents and authorization, but with two required UUID parameters and no schema descriptions it leaves parameter meaning unresolved. For a simple read tool that is mostly adequate, but not fully complete.

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 0%, and neither `company` nor `teammate` is explained in the description. The only hints are contextual phrases like 'this AI employee' and 'company owner,' which are not enough to clarify the two required UUID parameters.

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 opens with a specific verb and resource: listing people who can DM this AI employee in Slack, and it adds the returned list revision and `people` data. It is distinguishable from the sibling update tool, though it does not explicitly name that sibling.

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?

It gives a prerequisite (company owner or administrator) and an implied use case: choosing from people Summer has seen in selected channels. It does not state when to use this versus `summer_teammates_slack_dms_update` or `summer_teammates_list`, nor 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 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