Skip to main content
Glama
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 cancellation requests and how each ended: paused, renewal moved later, kept, cancelled, or a pause offered with no answer yet

summer_reports_cancellations
Read-onlyIdempotent

Read cancellation requests and how each ended: paused, renewal moved later, kept, cancelled, or a pause offered with no answer yet. The investigating agent marks each request; the approved plan option sets the outcome. revenue:true adds each saved plan's renewal amount and the paid renewals collected since the save (before refunds), read from live billing, plus gross totals. 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>"
    },
    "name": "summer_reports_cancellations"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
companyYes
revenueNo
environmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context: outcomes are derived from investigator marks and the approved plan option, revenue figures come from live billing, paid renewals are counted before refunds, and nothing is mutated. Only minor gaps (volume/pagination, latency) remain.

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

Conciseness3/5

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

The first sentence repeats the title verbatim, which is wasted space, and the closing 'Changes nothing' is a fragment. The revenue clause is dense but front-loaded and earns its place.

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 convey the categories returned and the revenue add-on contents. It omits record granularity, ordering, and any hint of result size, leaving the agent with an incomplete picture of what arrives.

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 0%, so the description must compensate, and it thoroughly defines revenue:true (saved-plan renewal amount, paid renewals since save, refunds excluded, gross totals). However, days, company, and environment are not explained beyond self-evident UUID and enum values.

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) and resource (cancellation requests) and enumerates the exact outcome categories returned (paused, renewal moved later, kept, cancelled, no answer). This makes it unmistakable against sibling report tools like commitments, credits, or delivery.

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 when-to-use or when-not guidance, and no sibling alternative is named. The revenue flag hints at when to include billing data, but the agent gets no steering on choosing this tool over other reports or on prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources