Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Pause the assistant in one conversation so a person can take over, or ask it to resume

summer_messenger_conversations_assistant
Destructive

Pause the assistant in one conversation so a person can take over, or ask it to resume. Pausing stops automatic replies immediately.

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>",
      "conversation": "<conversation>",
      "paused": "<paused>"
    },
    "name": "summer_messenger_conversations_assistant"
  }
}

Input Schema

NameRequiredDescriptionDefault
pausedYes
companyYesSummer company ID
environmentYesEnvironment that owns the resource
conversationYes
idempotency_keyNoReuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, destructive, non-idempotent, open-world behavior, so the bar is lower. The description adds real value with the immediate-effect statement for pausing, but leaves unexplained why a reversible pause/resume toggle is flagged destructive, what happens to messages already in flight, and why an idempotency_key exists alongside idempotentHint=false.

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?

Two short sentences, action and scope front-loaded, and the second sentence adds the non-obvious immediacy detail rather than restating the title. No filler.

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 five-parameter mutation with no output schema and a destructive annotation, the description omits the paused=true/false mapping, permission requirements, and any statement about what the call returns or how idempotency_key should be used on retries. Adequate to identify the tool, but not enough to invoke it confidently in edge cases.

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%: company, environment, and idempotency_key are documented in the schema, while the critical `paused` boolean and `conversation` UUID carry no schema description. The description implies the boolean direction (pause vs. resume) but never states explicitly that paused=true pauses and paused=false resumes, which is the single most important semantic here.

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 action (pause/resume) on a specific resource (the assistant) scoped explicitly to 'one conversation', which separates it from the sibling summer_messenger_assistant_update that likely governs the assistant globally. It never names that sibling, so the differentiation is inferable rather than stated.

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?

"So a person can take over" gives an implied usage context (human handoff), and "Pausing stops automatic replies immediately" hints at the effect of the true case. There is no explicit when-to-use/when-not-to-use guidance, no mention of the global assistant update sibling, and no prerequisite information.

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