Skip to main content
Glama

ServiceSchedule

by io.github.everyai-com
OverviewDiscussionsAdmin

Seasonal checklist

seasonal_checklist
Read-onlyIdempotent

Generate a preventive car checklist for spring, summer, fall or winter, grouped by area (tires, battery, fluids, wipers and more) and tuned for a hot, cold or mixed climate. Use when getting a car ready for the season ahead. Do NOT use for mileage-based maintenance status (use due_services).

Input Schema

NameRequiredDescriptionDefault
seasonYesSeason to prepare for
climateNoLocal climate: 'hot', 'cold' or 'mixed' (default)

Output Schema

NameRequiredDescriptionDefault
noteYesItem count and preventive-only caveat
seasonYesSeason the checklist covers
climateYesClimate the checklist is tuned for
checklistYesChecks grouped by area

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / climate / description
      Previous value: -"Local climate, default mixed"New value: +"Local climate: 'hot', 'cold' or 'mixed' (default)"
    • changedInput schema / properties / season / description
      Previous value: -"Season to plan for"New value: +"Season to prepare for"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "checklist": {
+      "description": "Checks grouped by area",
+      "items": {
+        "properties": {
+          "area": {
+            "description": "Area name, e.g. 'Tires'",
+            "type": "string"
+          },
+          "items": {
+            "description": "Checks for this area",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "area",
+          "items"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "climate": {
+      "description": "Climate the checklist is tuned for",
+      "enum": [
+        "hot",
+        "cold",
+        "mixed"
+      ],
+      "type": "string"
+    },
+    "note": {
+      "description": "Item count and preventive-only caveat",
+      "type": "string"
+    },
+    "season": {
+      "description": "Season the checklist covers",
+      "enum": [
+        "spring",
+        "summer",
+        "fall",
+        "winter"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "season",
+    "climate",
+    "checklist",
+    "note"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "checklist": {
-      "description": "List of checks grouped by area",
-      "items": {
-        "properties": {
-          "area": {
-            "description": "The area of the car to check (e.g., battery, tires)",
-            "type": "string"
-          },
-          "checks": {
-            "description": "List of specific checks to perform in this area",
-            "items": {
-              "description": "A specific check to perform",
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "required": [
-          "area",
-          "checks"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "climate": {
-      "description": "The climate for which the checklist is tailored",
-      "type": "string"
-    },
-    "season": {
-      "description": "The season for which the checklist is generated",
-      "type": "string"
-    }
-  },
-  "required": [
-    "season",
-    "climate",
-    "checklist"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "checklist": {
+      "description": "List of checks grouped by area",
+      "items": {
+        "properties": {
+          "area": {
+            "description": "The area of the car to check (e.g., battery, tires)",
+            "type": "string"
+          },
+          "checks": {
+            "description": "List of specific checks to perform in this area",
+            "items": {
+              "description": "A specific check to perform",
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "area",
+          "checks"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "climate": {
+      "description": "The climate for which the checklist is tailored",
+      "type": "string"
+    },
+    "season": {
+      "description": "The season for which the checklist is generated",
+      "type": "string"
+    }
+  },
+  "required": [
+    "season",
+    "climate",
+    "checklist"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuine value beyond that by disclosing the output shape (grouped by area such as tires, battery, fluids, wipers) and that results are tuned to climate, though it says nothing about length or format of the checklist beyond grouping.

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?

Three sentences with no filler: the output scope is front-loaded, then usage, then the exclusion. Every sentence earns its place and the routing instruction comes last where it is easy to act on.

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

Completeness5/5

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

An output schema exists, so return values need not be explained. With 2 enums fully documented in the schema and the description covering purpose, usage, and the sibling boundary, nothing an agent needs to call this tool correctly is missing.

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 100% and both parameters carry descriptions plus enums, so the schema does the heavy lifting. The description restates the season and climate dimensions and notes 'mixed' is the default, which is minor added meaning rather than new syntax or constraints. 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?

States a specific verb and resource ('Generate a preventive car checklist') plus the scoping dimensions (season, climate, grouped by area). It explicitly distinguishes itself from the sibling due_services, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives the positive trigger ('getting a car ready for the season ahead') and an explicit exclusion with the alternative named ('Do NOT use for mileage-based maintenance status (use due_services)'). This is the full when/when-not/alternative pattern.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ServiceSchedule 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