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.

Queue fresh research for the exact pending-plan preview, up to 100 tickets

summer_autonomy_plans_refresh

Destructive

Queue fresh research for the exact pending-plan preview, up to 100 tickets. Each fresh plan follows the ordinary auto-run eligibility rule. auto_run:true (matching the preview) picks only plans that could run on their own. Never replays old effects. Requires a new preview if work changed; successful repeats return the original 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_autonomy_plans_refresh"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026
- addedInput schema / properties / auto_run
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructive=true, openWorld=true, non-read-only; the description adds real value beyond them: the 100-ticket ceiling, that old effects are never replayed, that stale work invalidates the preview, and that successful repeats return the original receipt. What is missing is the blast radius (what exactly is queued/created and whether it can be undone). There is a mild tension with idempotentHint=false, since 'successful repeats return the original receipt' describes dedupe behavior, but it is framed as a narrow repeat case rather than a general contradiction.

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?

Front-loaded with purpose and scope, then eligibility, then safety/repeat semantics — every sentence carries information. The staccato fragments ("Never replays old effects.") read tersely but waste no words.

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?

For a destructive, open-world, 6-parameter mutation with no output schema, the description covers eligibility and repeat behavior but omits what the operation actually creates, whether it is reversible, and the meaning of missing_only. An agent can call it correctly only if it already understands the preview workflow.

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 50%; the description explains auto_run (only plans that could run autonomously, mirroring the preview) and implies preview_hash must match a current preview, which compensates partially. missing_only (default true) and idempotency_key are left entirely to the schema, so documentation is incomplete but adequate.

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 ("Queue fresh research for the exact pending-plan preview, up to 100 tickets") and scopes it to a bounded batch. It implicitly contrasts with the sibling summer_autonomy_plans_preview (this one refreshes/queues, the preview only previews), but never names the sibling explicitly.

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?

"Requires a new preview if work changed" tells the agent that a prior preview_hash is a precondition, and the auto_run sentence ties the flag to the preview's own setting. No explicit statement of when NOT to use it versus preview/policy_update, but the prerequisites make the intended workflow clear.

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?