ServiceSchedule

Service cost estimate

service_cost_estimate

Read-onlyIdempotent

Estimate typical US parts-and-labor price ranges (USD) for a list of car maintenance services at an economy, mid or luxury shop, with low and high totals. Use when budgeting for known services. An estimate, not a quote. Do NOT use to find which services are due (use due_services).

Input Schema

Name	Required	Description	Default
`tier`	No	Shop tier: 'economy' (x0.85), 'mid' (default) or 'luxury' (x1.6)
`services`	Yes	Service ids to price (duplicates ignored), e.g. ["oil_change","brake_inspection"]

Output Schema

Name	Required	Description
`note`	Yes	Summary of what was priced
`tier`	Yes	Shop tier used for pricing
`items`	Yes	Price range per service in USD
`total_low`	Yes	Sum of low prices, USD
`total_high`	Yes	Sum of high prices, USD
`source_note`	Yes	Source and estimate-not-quote caveat

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 10, 2026

changedInput schema / properties / services / description

Previous value: -"Service ids to price, e.g. oil_change"New value: +"Service ids to price (duplicates ignored), e.g. [\"oil_change\",\"brake_inspection\"]"

addedInput schema / properties / services / items / enum

Added value: +[
+  "oil_change",
+  "tire_rotation",
+  "brake_inspection",
+  "air_filter",
+  "cabin_filter",
+  "coolant_service",
+  "spark_plugs",
+  "transmission_service",
+  "battery_check"
+]

addedInput schema / properties / services / minItems
```
Added value: +1
```

changedInput schema / properties / tier / description

Previous value: -"Shop tier, default mid"New value: +"Shop tier: 'economy' (x0.85), 'mid' (default) or 'luxury' (x1.6)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "description": "Price range per service in USD",
+      "items": {
+        "properties": {
+          "high": {
+            "description": "High end of the typical price, USD",
+            "type": "number"
+          },
+          "id": {
+            "description": "Service id",
+            "enum": [
+              "oil_change",
+              "tire_rotation",
+              "brake_inspection",
+              "air_filter",
+              "cabin_filter",
+              "coolant_service",
+              "spark_plugs",
+              "transmission_service",
+              "battery_check"
+            ],
+            "type": "string"
+          },
+          "low": {
+            "description": "Low end of the typical price, USD",
+            "type": "number"
+          },
+          "name": {
+            "description": "Service name",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "low",
+          "high"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Summary of what was priced",
+      "type": "string"
+    },
+    "source_note": {
+      "description": "Source and estimate-not-quote caveat",
+      "type": "string"
+    },
+    "tier": {
+      "description": "Shop tier used for pricing",
+      "enum": [
+        "economy",
+        "mid",
+        "luxury"
+      ],
+      "type": "string"
+    },
+    "total_high": {
+      "description": "Sum of high prices, USD",
+      "type": "number"
+    },
+    "total_low": {
+      "description": "Sum of low prices, USD",
+      "type": "number"
+    }
+  },
+  "required": [
+    "tier",
+    "items",
+    "total_low",
+    "total_high",
+    "note",
+    "source_note"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "estimates": {
-      "description": "List of estimated price ranges for each service.",
-      "items": {
-        "properties": {
-          "range": {
-            "description": "The estimated price range for the service.",
-            "properties": {
-              "max": {
-                "description": "The maximum estimated price.",
-                "type": "number"
-              },
-              "min": {
-                "description": "The minimum estimated price.",
-                "type": "number"
-              }
-            },
-            "required": [
-              "min",
-              "max"
-            ],
-            "type": "object"
-          },
-          "service": {
-            "description": "The service id, e.g. oil_change.",
-            "type": "string"
-          }
-        },
-        "required": [
-          "service",
-          "range"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total": {
-      "description": "The estimated total price range for all services.",
-      "properties": {
-        "max": {
-          "description": "The maximum estimated total price.",
-          "type": "number"
-        },
-        "min": {
-          "description": "The minimum estimated total price.",
-          "type": "number"
-        }
-      },
-      "required": [
-        "min",
-        "max"
-      ],
-      "type": "object"
-    }
-  },
-  "required": [
-    "estimates",
-    "total"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "estimates": {
+      "description": "List of estimated price ranges for each service.",
+      "items": {
+        "properties": {
+          "range": {
+            "description": "The estimated price range for the service.",
+            "properties": {
+              "max": {
+                "description": "The maximum estimated price.",
+                "type": "number"
+              },
+              "min": {
+                "description": "The minimum estimated price.",
+                "type": "number"
+              }
+            },
+            "required": [
+              "min",
+              "max"
+            ],
+            "type": "object"
+          },
+          "service": {
+            "description": "The service id, e.g. oil_change.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "service",
+          "range"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "The estimated total price range for all services.",
+      "properties": {
+        "max": {
+          "description": "The maximum estimated total price.",
+          "type": "number"
+        },
+        "min": {
+          "description": "The minimum estimated total price.",
+          "type": "number"
+        }
+      },
+      "required": [
+        "min",
+        "max"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "estimates",
+    "total"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds value beyond that by clarifying the output nature (low/high ranges, USD, estimate vs quote) and geographic scope (US). It stops short of detailing output format, but with the output schema present that is not required.

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?

Four short sentences, front-loaded with purpose then usage then exclusion. No filler; each sentence carries distinct, decision-relevant information.

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?

For a simple read-only, two-parameter estimation tool with a defined output schema, the description covers purpose, scope, usage conditions, and the key alternative tool. Nothing an agent needs to call it 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 description coverage is 100%, so the parameters (services list and tier enum) are fully documented in the schema, including the tier multipliers. The description only restates the tier options and the service list at a high level, adding no syntax or format detail beyond the schema. 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 (Estimate), resource (US parts-and-labor price ranges in USD), and scope (tiers, low/high totals) for car maintenance services. It also distinguishes itself from the sibling due_services by name, so an agent can separate it from related tools without opening schemas.

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?

Explicitly states when to use it (budgeting for known services), sets expectation (an estimate, not a quote), and gives a clear when-not with the alternative: 'Do NOT use to find which services are due (use due_services).' This is exactly the routing guidance an agent needs.

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

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

Service cost estimate

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources