Skip to main content
Glama
Sign In

Summer

by ai.gosummer.api
OverviewDiscussionsAdmin
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.

Legacy channel policy only; unavailable after an explicit company-policy replacement

summer_messenger_autonomy_backfill_preview
Read-onlyIdempotent

Legacy channel policy only; unavailable after an explicit company-policy replacement. Preview existing Messenger work under saved autonomy settings: counts, a plan confidence histogram and a preview_hash. Returns no messages or customer records. Starts nothing. Up to 100 items per apply batch; totals cover all matching work.

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

Input Schema

NameRequiredDescriptionDefault
companyYesSummer company ID
environmentYesEnvironment that owns the resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive; the description adds real value beyond them by specifying the returned shape, stating 'returns no messages or customer records', and confirming 'starts nothing'. The 'up to 100 items per apply batch' figure adds operational context not present in annotations or schema.

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?

Every sentence carries information and there is no filler, but the content is front-loaded with a legacy/deprecation caveat rather than the primary action, and the telegraphic 'Starts nothing.' fragments read awkwardly. Its size is appropriate for a two-parameter read tool.

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?

With no output schema, the description correctly compensates by naming what is returned and what is explicitly not returned, plus the batch-size limit. What is missing is how this preview relates to the companion apply tool and whether the preview_hash is a required input there.

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 description coverage is 100% with only two parameters (company UUID, environment enum), both fully documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

The description states a specific verb and resource: preview existing Messenger work under saved autonomy settings, with named outputs (counts, plan confidence histogram, preview_hash). That is clearly distinguishable from the apply sibling, but the sibling itself is never named, so the agent must infer the pairing.

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?

The only usage signal is a 'when not to use' condition ('unavailable after an explicit company-policy replacement'), which is genuinely useful but framed as a deprecation notice. There is no explicit 'use this before/alongside X' routing to summer_messenger_autonomy_backfill_apply or to the other autonomy preview tools.

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

All Summer toolsInspect
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