Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Choose who Summer reads Slack as, with the revision from slack

summer_slack_reader_update

Choose who Summer reads Slack as, with the revision from slack.reader.read and a reason. 'me' uses the caller's own connected Slack account; nobody can choose another person's account. Summer reads only the selected channels that account can see. Sends no message.

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>",
      "revision": "<revision>",
      "reader": "<reader>",
      "reason": "<reason>"
    },
    "name": "summer_slack_reader_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
readerYes
reasonYes
companyYesSummer company ID
revisionYesCurrent revision from slack.reader.read; 0 before the first save.
teammate_idNoAn active teammate from teammates.list when reader is 'teammate'.
idempotency_keyNoReuse the same key when retrying the same change

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 establish that this is a non-read-only, non-destructive, open-world mutation. The description adds useful behavior: it sends no message, reads only selected channels visible to the chosen account, and restricts choosing another person's account.

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-loaded around the core action, with the security and side-effect constraints stated efficiently. It has little waste, though the wording around account selection could be clearer.

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?

For a six-parameter mutation with no output schema, the description covers the main effect and some safety constraints. It does not explain revision conflicts, idempotency behavior, or how connection versus teammate readers differ, which leaves important operational context incomplete.

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?

The schema covers company, revision, teammate_id, and idempotency_key, but the reader enum lacks per-value descriptions. The description explains 'me' and revision semantics, yet leaves 'connection' and 'teammate' unclear, and its statement that nobody can choose another person's account appears to conflict with the teammate/teammate_id option.

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 action and resource: choosing who Summer reads Slack as, using a revision from slack.reader.read. This distinguishes it from the read-side sibling and from other Slack update tools, though it does not explicitly name the closest alternatives.

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 implies a read-then-update workflow by requiring the revision from slack.reader.read, and it explains that 'me' uses the caller's own account. However, it does not explicitly say when to choose this tool over slack_reader_read, slack_identity_update, or slack_sender_update.

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