Summer

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.

Stop an exact investigation owned by this case, preserving its evidence and history

summer_investigations_stop

Destructive

Stop an exact investigation owned by this case, preserving its evidence and history. Cannot stop execution runs. A stop request is not a finished cancellation: read investigations.list until the run is cancelled or completed, then use investigations.request with current guidance to rerun.

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>",
      "run": "<run>"
    },
    "name": "summer_investigations_stop"
  }
}

Input Schema

Name	Required	Description
`run`	Yes
`case`	Yes
`company`	Yes	Summer company ID
`environment`	Yes	Environment that owns the resource
`idempotency_key`	No	Reuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: destruction is scoped (evidence and history preserved, which tempers destructiveHint=true), async semantics are disclosed (a stop request is not a finished cancellation), and the required follow-up polling is named. No contradiction with destructiveHint or idempotentHint.

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?

Three tight sentences, front-loaded with the scope and preservation guarantee, with the async caveat and rerun path in sequence. No filler, though the polling instruction could be slightly more compact.

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

Completeness5/5

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

For a destructive, open-world, non-idempotent, five-parameter tool with no output schema, the description covers the essentials: scope restriction, what is preserved, async termination semantics, and the verification path. Nothing needed to invoke or interpret it correctly is missing.

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 60% and the description clarifies the crucial scoping: the run must be one owned by this case, which explains the case+run pairing semantically rather than structurally. It says nothing about company/environment or the idempotency_key, despite idempotentHint=false, so it only partially compensates.

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?

Specific verb (stop) plus a precisely scoped resource (an exact investigation owned by this case), and it states the preservation guarantee. It also distinguishes itself from sibling error by excluding execution runs, so an agent can separate it from summer_investigations_request without opening schemas.

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

Usage Guidelines5/5

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

Explicit when-to-use (to stop a case-owned investigation), an explicit exclusion (cannot stop execution runs), and a follow-up path: poll investigations.list, then use investigations.request with current guidance to rerun. That is a complete when/when-not/alternative routing.

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.

Resources

Need Help?