Summer

Read paginated original issue/message references behind service counts and timing samples, with date/channel/hour filters in the company timezone

summer_reports_samples_list

Read-onlyIdempotent

Read paginated original issue/message references behind service counts and timing samples, with date/channel/hour filters in the company timezone. Read-only Intercom archive projections are excluded from operational workload counts. No messages are sent or marked read.

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

Input Schema

Name	Required	Description	Default
`from`	No
`hour`	No
`limit`	No
`offset`	No
`channel`	No
`company`	Yes
`measure`	Yes
`through`	No
`weekday`	No
`observedAt`	No
`environment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / measure / enum

Previous value: -[
-  "handled",
-  "approved",
-  "approvedCompleted",
-  "fullyAutomatic",
-  "incoming",
-  "resolved",
-  "inbound",
-  "answered",
-  "unanswered",
-  "response",
-  "firstReply",
-  "resolution"
-]New value: +[
+  "handled",
+  "approved",
+  "approvedCompleted",
+  "fullyAutomatic",
+  "closedWithoutPerson",
+  "incoming",
+  "resolved",
+  "inbound",
+  "answered",
+  "unanswered",
+  "response",
+  "firstReply",
+  "resolution"
+]

AddedOct 23, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With readOnlyHint/idempotentHint already covering safety, the description adds real value: filters are evaluated in the company timezone, read-only Intercom archive projections are excluded from operational workload counts, and no messages are sent or marked read. It still does not describe pagination behavior or ordering, which is the main residual gap.

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

Conciseness5/5

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

Two tight sentences, purpose front-loaded, then the two scope caveats that matter. Nothing is wasted, and the redundant-with-annotations line about not marking messages read is short and still clarifying for a messaging-adjacent tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists and the description only gestures at what is returned ('original issue/message references') without shape or fields. Combined with 0% schema coverage on 11 parameters and an opaque required enum, an agent cannot reliably construct a correct call from this definition.

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 coverage is 0% across 11 parameters, so the description carries the full burden and largely fails. It mentions 'date/channel/hour filters in the company timezone', loosely mapping to from/through/hour/channel, but gives no meaning for the 13-value required 'measure' enum, nor for weekday, observedAt, limit, offset, company, or environment.

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: reading paginated original issue/message references that back service counts and timing samples. It is clearly a read/list drill-down tool, though it never names its report siblings (summer_reports_service_metrics, summer_reports_agent_timing) explicitly, so the relationship is only implied by 'behind service counts and timing samples'.

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 only implied: 'behind service counts and timing samples' suggests this is the drill-down companion for report aggregates, but there is no explicit when-to-use statement, no when-not-to-use, and no alternative tool named. An agent must infer the routing from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Summer tools Inspect

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.