Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Preview the complete replacement execution policy

summer_autonomy_policy_preview
Read-onlyIdempotent

Preview the complete replacement execution policy. Conversation reply grants remain separate; explicit communication review exceptions apply to replies too. Optional partial (run the leading qualifying steps, leave the rest with a person) is off when omitted. Money limits (refund, credit and daily totals in cents) default to $200 per refund, $100 per credit and $500 in 24 hours when omitted. Returns an exact preview hash; changes nothing.

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>",
      "version": "<version>",
      "settings": "<settings>"
    },
    "name": "summer_autonomy_policy_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesSummer company ID
versionYes
settingsYes
environmentYesEnvironment that owns the resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / settings / properties / money / description
      Previous value: -"Money limits for auto-run. Charges and promotions always wait for a person."New value: +"Money limits for auto-run, in whole cents. Omitted: a refund up to 20000 ($200), a credit up to 10000 ($100) and 50000 ($500) in any 24 hours. Set the limits to 0 to make all money wait for a person. Charges and promotions always wait for a person."
  2. Changed1 schema field changed
    • addedInput schema / properties / settings / properties / exceptions / items / properties / family
      Added value: +{
+  "description": "An action family: reply, closure, record, vendor_contact, clinician_note, address_cancel or money. With mode review, the rule holds every action in the family (a kill switch). An automatic family rule does not lift the Slack hold unless it also names the slack channel.",
+  "enum": [
+    "reply",
+    "closure",
+    "record",
+    "vendor_contact",
+    "clinician_note",
+    "address_cancel",
+    "money"
+  ],
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / settings / properties / money
      Added value: +{
+  "additionalProperties": false,
+  "description": "Money limits for auto-run. Charges and promotions always wait for a person.",
+  "properties": {
+    "creditCentsMax": {
+      "description": "Largest single account credit that may run automatically. Omitted: credits wait for a person.",
+      "maximum": 1000000,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "dailyCentsMax": {
+      "description": "Most refunds and credits that auto-run may approve in any 24 hours, across the company and environment.",
+      "maximum": 1000000,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "refundCentsMax": {
+      "description": "Largest single refund that may run automatically. Omitted: refunds wait for a person.",
+      "maximum": 1000000,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "dailyCentsMax"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / settings / properties / partial
      Added value: +{
+  "description": "When true, auto-run may run the leading steps of a plan that qualify and leave the remaining steps, and every case closure, waiting for a person. Off when omitted.",
+  "type": "boolean"
+}
  4. Added

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; the description still adds real behavior: 'Conversation reply grants remain separate; explicit communication review exceptions apply to replies too' and the confirmation that it returns an exact hash and mutates nothing. The defaults for partial and money limits largely restate schema text, which holds it back from a 5.

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?

Purpose is front-loaded in the first sentence and each subsequent sentence carries a distinct rule (reply grants, partial default, money defaults, return value). It is slightly dense and repeats default values that the schema already states, costing a point.

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?

This is a complex nested preview tool with 4 required params, nested objects and no output schema. The description covers the overall contract and some defaults, but leaves key semantics (threshold meaning/units, version usage, mode review vs automatic, how exception rules interact) to be inferred.

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%. The description explains the omitted-behavior of 'partial' and the money defaults, but those are already in the schema, while undocumented parameters that matter most — 'version' (presumably optimistic concurrency) and 'default.mode'/'threshold' — get no explanation of what they mean or how conflicts are handled.

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 the complete replacement execution policy') and closes with 'Returns an exact preview hash; changes nothing', which separates it from the mutating summer_autonomy_policy_update sibling. It never names the sibling or the family-level preview explicitly, so the differentiation is implied 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?

'Preview' plus 'changes nothing' hints that this is the safe pre-flight step before summer_autonomy_policy_update, but the description never says to call it first or when to skip it. It also doesn't distinguish this from summer_autonomy_policy_family_preview.

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