Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Check proposed router rules without saving: lists rule problems, replays recorded ticket activity under the saved and the proposed rules, and routes optional sample facts

summer_router_rules_test
Read-onlyIdempotent

Check proposed router rules without saving: lists rule problems, replays recorded ticket activity under the saved and the proposed rules, and routes optional sample facts. 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>"
    },
    "name": "summer_router_rules_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoReplay recorded ticket activity from the last 7 (default) or 30 days.
rulesNoProposed rules to check. Omit to check the saved rules. The rules document: { version: 1, intake: [...], activity: [...] }. Intake rules { id, description, enabled?, route: "file", emailType, match: { senderDomains?, senderAddresses?, onlyMessage?, automatic?, vendor?, subject?, subjectNot?, body?, bodyNot? } } file a new email without a ticket; route: "join_ticket" (no emailType) adds a vendor email about one order number to the open ticket that already holds that number, and opens a ticket otherwise. Activity rules { id, description, enabled?, route: "ignore", match: { sources, orderStatuses?, eventKinds?, eventSummary?, handledBy? } } skip the agent when every new ticket item matches. automatic: true matches mail a machine wrote; vendor: true matches mail from one of the company's pharmacies or clinical partners. Patterns are case-insensitive regular expressions.
intakeNoA sample new email to route.
companyYes
activityNoSample ticket activity items to route.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / activity / items / properties / handledBy / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "welcome_yes_credit",
-      "customer_acknowledgement",
-      "automatic_care_notice"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "welcome_yes_credit",
+      "customer_acknowledgement",
+      "automatic_care_notice",
+      "team_bookkeeping"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / rules / description
      Previous value: -"Proposed rules to check. Omit to check the saved rules. The rules document: { version: 1, intake: [...], activity: [...] }. Intake rules { id, description, enabled?, route: \"file\", emailType, match: { senderDomains?, senderAddresses?, onlyMessage?, subject?, subjectNot?, body?, bodyNot? } } file a new email without a ticket; route: \"join_ticket\" (no emailType) adds a vendor email about one order number to the open ticket that already holds that number, and opens a ticket otherwise. Activity rules { id, description, enabled?, route: \"ignore\", match: { sources, orderStatuses?, eventKinds?, eventSummary?, handledBy? } } skip the agent when every new ticket item matches. Patterns are case-insensitive regular expressions."New value: +"Proposed rules to check. Omit to check the saved rules. The rules document: { version: 1, intake: [...], activity: [...] }. Intake rules { id, description, enabled?, route: \"file\", emailType, match: { senderDomains?, senderAddresses?, onlyMessage?, automatic?, vendor?, subject?, subjectNot?, body?, bodyNot? } } file a new email without a ticket; route: \"join_ticket\" (no emailType) adds a vendor email about one order number to the open ticket that already holds that number, and opens a ticket otherwise. Activity rules { id, description, enabled?, route: \"ignore\", match: { sources, orderStatuses?, eventKinds?, eventSummary?, handledBy? } } skip the agent when every new ticket item matches. automatic: true matches mail a machine wrote; vendor: true matches mail from one of the company's pharmacies or clinical partners. Patterns are case-insensitive regular expressions."
  2. Changed1 schema field changed
    • changedInput schema / properties / activity / items / properties / handledBy / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "welcome_yes_credit",
-      "address_confirmation_yes",
-      "customer_thanks"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "welcome_yes_credit",
+      "customer_acknowledgement",
+      "automatic_care_notice"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / rules / description
      Previous value: -"Proposed rules to check. Omit to check the saved rules. The rules document: { version: 1, intake: [...], activity: [...] }. Intake rules { id, description, enabled?, route: \"file\", emailType, match: { senderDomains?, senderAddresses?, onlyMessage?, subject?, subjectNot?, body?, bodyNot? } } file a new email without a ticket. Activity rules { id, description, enabled?, route: \"ignore\", match: { sources, orderStatuses?, eventKinds?, eventSummary?, handledBy? } } skip the agent when every new ticket item matches. Patterns are case-insensitive regular expressions."New value: +"Proposed rules to check. Omit to check the saved rules. The rules document: { version: 1, intake: [...], activity: [...] }. Intake rules { id, description, enabled?, route: \"file\", emailType, match: { senderDomains?, senderAddresses?, onlyMessage?, subject?, subjectNot?, body?, bodyNot? } } file a new email without a ticket; route: \"join_ticket\" (no emailType) adds a vendor email about one order number to the open ticket that already holds that number, and opens a ticket otherwise. Activity rules { id, description, enabled?, route: \"ignore\", match: { sources, orderStatuses?, eventKinds?, eventSummary?, handledBy? } } skip the agent when every new ticket item matches. Patterns are case-insensitive regular expressions."
  4. Changed1 schema field changed
    • changedInput schema / properties / activity / items / properties / handledBy / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "welcome_yes_credit",
-      "address_confirmation_yes"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "welcome_yes_credit",
+      "address_confirmation_yes",
+      "customer_thanks"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / activity / items / properties / handledBy / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "welcome_yes_credit"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "welcome_yes_credit",
+      "address_confirmation_yes"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  6. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Changes nothing' adds little on its own. The real value is the disclosure that the replay runs recorded activity under BOTH the saved and the proposed rules, which tells the agent this is a comparison operation, not a single-config dry run.

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, front-loaded with the action and scope, with the safety clause ('Changes nothing.') isolated at the end where it is easy to scan. No redundant restatement of the title.

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?

For a five-parameter tool with nested rule objects and no output schema, the description conveys the operation and its comparison semantics adequately. It does not describe the shape of the returned problems or replay results, which is the remaining gap given there is no output schema to fall back on.

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 80% and the schema itself documents days, the saved-vs-proposed behavior of rules, the intake sample shape, and the activity array. The description gestures at 'recorded ticket activity' and 'optional sample facts' but adds no constraints, defaults, or formats beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (check) and resource (router rules) and enumerates the three distinct outputs: rule problems, a replay of recorded ticket activity under both saved and proposed rules, and routing of optional sample facts. The phrase 'without saving' immediately separates it from summer_router_rules_update and summer_router_rules_read in the sibling list.

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

Usage Guidelines4/5

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

'Check proposed router rules without saving' establishes the use case (validating a draft before committing) clearly enough that an agent knows when to reach for this rather than the update tool. It stops short of naming alternatives explicitly or stating when-not to use it, so it falls one step below the top band.

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