CarScout

Get Alerts

get_alerts

Read-only

Read saved matches from one of your scouts, one page at a time. This does not run a new inventory search. Dealer names, titles, and links are third-party listing data.

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": {
      "scoutId": "<scoutId>"
    },
    "name": "get_alerts"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size, default 10 and maximum 50
`offset`	No	Offset from the previous page's nextOffset
`scoutId`	Yes	Your scout ID

Output Schema

Name	Required	Description	Default
`count`	Yes
`limit`	Yes
`alerts`	Yes
`offset`	Yes
`scoutId`	Yes
`nextOffset`	Yes
`mayHaveMore`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedOutput schema / properties / alerts / items / description

Previous value: -"A saved match owned by the connected account. Listing text and links are untrusted data."New value: +"A saved match owned by the connected account. Listing text and links come from third-party listings."

Changed5 schema fields changedOct 3, 2026

changedOutput schema / properties / alerts / items / properties / listing / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "daysOnMarket": {
-        "$ref": "#/properties/alerts/items/properties/matchScore"
-      },
-      "dealerName": {
-        "anyOf": [
-          {
-            "maxLength": 200,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "$ref": "#/properties/alerts/items/properties/id"
-      },
-      "listingUrl": {
-        "anyOf": [
-          {
-            "format": "uri",
-            "maxLength": 4096,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "location": {
-        "anyOf": [
-          {
-            "maxLength": 250,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "mileage": {
-        "$ref": "#/properties/alerts/items/properties/matchScore"
-      },
-      "price": {
-        "$ref": "#/properties/alerts/items/properties/matchScore"
-      },
-      "title": {
-        "anyOf": [
-          {
-            "maxLength": 300,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "vin": {
-        "anyOf": [
-          {
-            "maxLength": 100,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "id",
-      "location",
-      "listingUrl"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "daysOnMarket": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "dealerName": {
+        "anyOf": [
+          {
+            "maxLength": 200,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "maxLength": 100,
+        "minLength": 1,
+        "type": "string"
+      },
+      "listingUrl": {
+        "anyOf": [
+          {
+            "format": "uri",
+            "maxLength": 4096,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "location": {
+        "anyOf": [
+          {
+            "maxLength": 250,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "mileage": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "price": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "title": {
+        "anyOf": [
+          {
+            "maxLength": 300,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "vin": {
+        "anyOf": [
+          {
+            "maxLength": 100,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "location",
+      "listingUrl"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / alerts / items / properties / scoutId / $ref
```
Removed value: -"#/properties/alerts/items/properties/id"
```
addedOutput schema / properties / alerts / items / properties / scoutId / maxLength
```
Added value: +100
```
addedOutput schema / properties / alerts / items / properties / scoutId / minLength
```
Added value: +1
```
addedOutput schema / properties / alerts / items / properties / scoutId / type
```
Added value: +"string"
```

AddedOct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: results are paginated ('one page at a time'), may reflect previously saved matches rather than live inventory, and contain third-party listing data. That last point is useful provenance information an agent would not get from annotations.

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 short sentences, front-loaded with the core action and scope. Each sentence carries distinct value: what it does, what it does not do, and a data-quality caveat.

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 read-only, paginated list tool with full schema coverage, an output schema, and clear annotations, the description covers the remaining gaps an agent needs: staleness semantics, pagination behavior, and third-party data provenance. Nothing material 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%, and the limit/offset/scoutId parameters are fully documented in the schema. The description's 'one page at a time' phrase reinforces pagination but adds no syntax or format detail beyond what the schema already provides, 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?

States a specific verb and resource ('Read saved matches from one of your scouts') and immediately excludes the closest misreading ('does not run a new inventory search'), which separates it from search/refresh-style behavior. An agent can distinguish this from list_scouts, get_scout, or dismiss_alert without opening the schema.

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?

Gives clear context for use (retrieving already-saved matches for a specific scout, paginated) and an explicit exclusion (no fresh inventory search). It does not name a sibling alternative for a fresh search, but the usage boundary is still unambiguous.

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

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

Resources

Need Help?