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.

Apply an exact backfill preview using saved settings

summer_messenger_autonomy_backfill_apply

Destructive

Apply an exact backfill preview using saved settings. Queue unanswered conversations and fresh investigations of qualifying pending plans, up to 100 items. Enabled assistants may reply; new plans follow saved auto-run settings. Skips paused, active, failed or uncertain work. Does not replay old executions. Requires the exact preview_hash; changed settings or work require a new preview. Repeating a successful hash returns its saved receipt.

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>",
      "preview_hash": "<preview_hash>"
    },
    "name": "summer_messenger_autonomy_backfill_apply"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior1/5

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

The description adds rich behavior beyond annotations: a 100-item cap, skipped statuses, no replay, assistant replies, and receipt on repeat. However, it says 'Repeating a successful hash returns its saved receipt,' which asserts idempotent behavior for repeated identical calls, while annotations declare idempotentHint=false. That is a direct contradiction, so score 1 per the rule.

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?

The description is front-loaded with the core action, then follows a tight sequence of behavioral constraints. There is no filler; every sentence adds a rule, limit, or outcome.

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 destructive, open-world tool with no output schema, it covers the main behavioral constraints and the repeat/receipt outcome. It could name the preview tool and explain idempotency_key usage more directly, but it is largely complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%; company, environment, and idempotency_key are documented in the schema. The description compensates for the undocumented preview_hash by stating it must be exact and that changed settings/work invalidate it, adding real meaning beyond the schema pattern.

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?

The description opens with a specific verb ('Apply') and resource ('exact backfill preview using saved settings'), then scopes the operation to queuing unanswered conversations and investigations up to 100 items. The preview_hash requirement clearly distinguishes it from the sibling preview tool.

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

Usage Guidelines4/5

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

It gives a clear prerequisite (exact preview_hash) and a when-not condition (changed settings or work require a new preview), plus scope limits. It stops short of naming summer_messenger_autonomy_backfill_preview explicitly as the alternative, so it is not fully explicit.

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?