Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Create, edit, retire or restore a saved reply with its expected revision and reason

summer_saved_replies_save
Destructive

Create, edit, retire or restore a saved reply with its expected revision and reason. Sends nothing. API reference: https://api.gosummer.ai/v1/openapi.json

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>",
      "id": "<id>",
      "expectedRevision": "<expectedRevision>",
      "name": "<name>",
      "body": "<body>",
      "retired": "<retired>",
      "reason": "<reason>"
    },
    "name": "summer_saved_replies_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyYes
nameYes
reasonYes
companyYes
retiredYes
idempotency_keyNoReuse the same key when retrying the same change
expectedRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructive=true, readOnly=false and openWorld=true; the description adds genuinely useful context ('Sends nothing') that prevents the agent from assuming a message is delivered. However it omits the important behaviors: what happens on a stale expectedRevision, whether restore means retired=false, and whether the id must pre-exist.

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?

Two tight sentences front-load the operations and the safety note; nothing is padded. The trailing API reference URL is of marginal value to an agent at call time, but it is short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An 8-parameter, 7-required destructive mutation with no output schema needs more than two sentences: the create/edit mode selection, revision-conflict behavior, and the meaning of retired are all unresolved. The description is not sufficient for an agent to invoke this safely on the first try.

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

Parameters2/5

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

Schema description coverage is only 13%, so the description carries the burden, yet it only alludes to expectedRevision and reason. The five other required parameters (company, id, name, body, retired) are left entirely to bare schema types, with no explanation of how id/name/body differ between create and edit or what retired=false means.

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?

Names a specific resource (saved reply) and the full set of operations it covers (create, edit, retire, restore), which is far more informative than the name alone. It does not explicitly distinguish itself from summer_saved_replies_list or summer_saved_replies_history, but the write-vs-read split is obvious from the verbs.

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

Usage Guidelines2/5

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

The phrase 'with its expected revision and reason' hints that a prior revision must be known, but there is no explicit statement of when to call this versus the list/history siblings, nor how to obtain expectedRevision before calling. Crucially, nothing explains how the agent chooses between create and edit with a single tool.

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