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.

Read the case chat with Summer: each question people asked about the case, oldest first, with its status and Summer's saved answer (the latest 10)

summer_cases_chat_list
Read-onlyIdempotent

Read the case chat with Summer: each question people asked about the case, oldest first, with its status and Summer's saved answer (the latest 10). An answer is Summer's explanation of its own work, not new evidence, approval or a customer outcome.

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_chat_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
companyYesSummer company ID
environmentYesEnvironment that owns the resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses two things the annotations cannot: the result is truncated to the latest 10 entries with no stated pagination, and ordering is oldest-first. The closing sentence also sets an important interpretive limit — an answer is Summer explaining its own work, not new evidence, approval, or a customer outcome — which prevents an agent from over-weighting the answers.

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?

Two tight sentences with the core scope front-loaded and the semantic caveat trailing. Slightly redundant with the tool title, which repeats the first sentence verbatim.

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 read-only list tool with no output schema, the description covers what is returned, the ordering, and the truncation cap, which is most of what an agent needs. The remaining gap is what to do about the 10-item limit — there is no mention of how to reach older questions.

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 67%: company and environment are documented inline, but the case UUID is not, and the description supplies no parameter guidance at all. With the schema doing most of the work, this is the baseline adequate case rather than a value-add.

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 verb and resource ('Read the case chat with Summer') and precisely enumerates the returned content: each question, oldest first, with status and the saved answer, capped at the latest 10. It does not explicitly name the sibling summer_cases_chat_ask as the alternative for posting a question, so sibling differentiation is left to the name.

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 implied — you call this to see what people asked about a case and what Summer answered — but there is no explicit 'use this when' statement, no exclusions, and no pointer to summer_cases_chat_ask for asking instead. An agent can infer the boundary but must do the work.

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