Summer

Create or edit guidebook details at the expected version

summer_guides_save

Destructive

Create or edit guidebook details at the expected version. Saves a private draft; does not publish.

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>",
      "expected_version": "<expected_version>",
      "settings": "<settings>",
      "reason": "<reason>"
    },
    "name": "summer_guides_save"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes
`company`	Yes	Summer company ID
`settings`	Yes
`idempotency_key`	No	Reuse the same key when retrying the same change
`expected_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / settings / properties / support_installation_id

Added value: +{
+  "anyOf": [
+    {
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed1 schema field changedOct 21, 2026
- addedInput schema / properties / settings / properties / hero_background
```
Added value: +{
+  "pattern": "^#[0-9a-fA-F]{6}$",
+  "type": "string"
+}
```
AddedOct 21, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The draft-only/non-publishing behavior is genuine context the annotations do not convey. However, the description never explains why destructiveHint=true (that saving overwrites existing guidebook settings), nor what happens when expected_version does not match the current server version — a critical failure mode for a mutation.

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 tight sentences with the core action first and the important draft-only caveat second. Nothing wasted, nothing buried.

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?

For a 5-parameter mutation with a required nested settings object, a required reason, an idempotency key, and no output schema, the description is far too thin. It omits how drafts are later published, how to recover from a version conflict, and what settings are mandatory.

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 coverage is only 40%, so the description must compensate — it does not. expected_version is alluded to only as 'the expected version' with no statement of behavior on mismatch, and required parameters such as reason (an audit justification) and the nested settings object are never explained.

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 verb pair (create or edit) and resource (guidebook details), plus the optimistic-concurrency framing 'at the expected version'. The clause 'does not publish' implicitly distinguishes it from summer_guides_publish, though no sibling is named outright.

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?

'Saves a private draft; does not publish' implies the when-to-use split versus summer_guides_publish, but the agent is left to infer the follow-up (that publish is required to go live) and receives no guidance on version-conflict handling or retry conditions.

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.