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.

Count latest pending plans per open ticket across the connected operations company, including partner/system/operator origins

summer_autonomy_plans_preview

Read-onlyIdempotent

Count latest pending plans per open ticket across the connected operations company, including partner/system/operator origins. Other tenants cover only their Messenger tickets. Returns aggregate scores, holds, coverage and an exact refresh preview; starts nothing. auto_run:true previews only plans that could run on their own under current auto-run settings.

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_autonomy_plans_preview"
  }
}

Input Schema

Name	Required	Description
`company`	Yes	Summer company ID
`auto_run`	No
`environment`	Yes	Environment that owns the resource
`missing_only`	No

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.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: it clarifies that even auto_run:true only previews and 'starts nothing', and that other tenants see only their Messenger tickets. It also enumerates the response shape (aggregate scores, holds, coverage, refresh preview), which is more than the annotations convey.

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 the count/scope statement, then the return shape, then the auto_run caveat; every sentence carries information. It is mildly redundant with the title, which restates the first sentence almost verbatim.

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 read-only preview with no output schema, the description supplies return contents and the no-side-effect guarantee, which is the core need. Gaps remain around missing_only semantics, what 'latest pending' means operationally, and the puzzling 'other tenants' scoping statement, so it is adequate rather than complete.

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%: company and environment are documented in the schema, while auto_run and missing_only are not. The description partially compensates by explaining auto_run's effect, but missing_only — a boolean defaulting to true — is left completely unexplained in both schema and description, which matters for a counting tool.

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: 'Count latest pending plans per open ticket across the connected operations company', plus the origin scope (partner/system/operator). The contrast with the mutation sibling is only implied via 'exact refresh preview; starts nothing' rather than naming summer_autonomy_plans_refresh, so sibling differentiation is inferable but not explicit.

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?

'starts nothing' and the auto_run note imply this is the safe pre-flight before a refresh, which is useful context. However, it never says explicitly 'use summer_autonomy_plans_refresh to apply' or when a caller would choose this over summer_autonomy_policy_preview, leaving the choice to inference.

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?