Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Read Slack messages queued for office hours on this exact case, their approved words, destination, scheduled opening and delivery result

summer_cases_queued_slack_list
Read-onlyIdempotent

Read Slack messages queued for office hours on this exact case, their approved words, destination, scheduled opening and delivery result. Changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
caseYes
companyYes
environmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description's 'Changes nothing' is aligned but largely redundant. It does add useful detail about what is returned (approved words, destination, scheduled opening, delivery result), but lacks pagination, sorting, or auth/rate-limit context.

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 front-loaded and brief, with no wasted preamble. 'Changes nothing' is slightly redundant given the readOnly annotation, but the sentence earns most of its place by listing the returned fields.

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?

Annotations cover the safety profile and the description lists the main returned data, which helps because there is no output schema. However, with three required parameters and no schema descriptions, the missing company/environment semantics leave a meaningful gap.

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%, so the description must compensate for all three required parameters. It hints at the 'case' parameter with 'on this exact case', but says nothing about the required company UUID or the staging/production environment enum.

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 ('Read'), a specific resource ('Slack messages queued for office hours on this exact case'), and the fields returned. This clearly distinguishes it from siblings like queued_texts_list and queued_slack_cancel without needing to name them.

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?

The intended usage is implied by the scope ('on this exact case'), but the description gives no explicit when-to-use guidance, exclusions, or comparison to the cancel/list alternatives. An agent can infer the use case but must still reason about alternatives.

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