Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Read one case or conversation with its original messages and related records

summer_cases_get
Read-onlyIdempotent

Read one case or conversation with its original messages and related records. Operational records include workspace with the current customer ticket and all owned issue references, plus the shared saved timeline, including original inbound phone transcripts, caller-supplied pharmacy intake and private tool receipts with attempts and results. Generated speech is not proof the caller heard it; saved intake is not resolution. The conversation field includes messages, other_threads and activity from the same case feed: original email From/To headers, Slack sender/channel, and care routing audience/direction/endpoints when recorded. Missing headers stay unknown; routing is display evidence, never reply authorization. The original case identity is retained. Includes conversationSentiment with happy, neutral, upset, angry, sad, mixed or unknown, confidence, exact evidence references, source, assessed_at and pending freshness; an estimate does not prove resolution. contact_sources lists each name, email and phone with its source (account, staff-saved or the website chat form) and a plain note; chat form details are self-reported, never identity proof or a reply address. Each customer_records.orders item has supply: paid plan months, each product's package days, the newest prescriptions with quantity, refills and days per fill (with its source), the shipment sequence of a split plan and a plain summary; unavailable:true means unknown, not none. Supply facts never give dosing.

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

Input Schema

NameRequiredDescriptionDefault
caseYes
afterNo
companyYesSummer company ID
environmentYesEnvironment that owns the resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the bar is lower. The description still adds real behavioral constraints beyond them: 'Generated speech is not proof the caller heard it; saved intake is not resolution,' 'routing is display evidence, never reply authorization,' chat form details are 'never identity proof or a reply address,' and 'unavailable:true means unknown, not none.' These are meaningful guardrails on how the returned data may be used. It does not cover pagination behavior despite an 'after' parameter, which keeps it below 5.

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

Conciseness2/5

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

The first sentence states purpose well, but the remainder is a dense, unstructured wall covering sentiment fields, contact sources, order supply details, and evidence caveats with no paragraphs or hierarchy. Much of it reads as output-schema documentation rather than front-loaded guidance for selecting and invoking the tool.

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?

With no output schema, the description does the work of explaining return fields in unusual depth, which is valuable. However, for a four-parameter read tool it is silent on the 'case' identifier semantics, the 'after' pagination cursor, and error behavior when a case is missing. It is rich on outputs but incomplete on inputs and operational behavior.

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 50%: company and environment are documented in the schema, but case and after are not. The description never mentions any parameter, not even the 'after' cursor that clearly controls pagination, so it does not compensate for the coverage gap. All of its text is directed at return-field interpretation rather than inputs.

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 opening sentence gives a specific verb and resource: 'Read one case or conversation with its original messages and related records.' An agent can tell it fetches a single case with its feed and related records. It does not distinguish itself from close siblings such as summer_cases_list, summer_cases_search, or summer_messenger_conversations_get, so sibling differentiation is missing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus summer_cases_list, summer_cases_search, or summer_cases_discussions_read. The phrase 'Read one case' implies you need an existing case ID, but the description never states the precondition or the alternative paths, leaving routing entirely to inference.

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