s&box watch

Search s&box packages

search_packages

Read-onlyIdempotent

Find public s&box games, maps, or libraries with live rankings, seven-day and cumulative game playtime, official game-jam membership, and canonical source URLs.

Input Schema

Name	Required	Description	Default
`jam`	No	Restrict games to an official s&box game jam.
`kind`	No		game
`sort`	No
`limit`	No
`query`	No

Output Schema

Name	Required	Description	Default
`kind`	Yes
`sort`	Yes
`query`	Yes
`total`	Yes
`results`	Yes
`generation`	Yes
`generatedAt`	Yes
`contentNotice`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026
- removedOutput schema / properties / results / items / properties / workshopId
```
Removed value: -{
-  "pattern": "^[1-9]\\d{0,19}$",
-  "type": "string"
-}
```
- removedOutput schema / properties / results / items / properties / workshopUrl
```
Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
```
Changed2 schema fields changedOct 13, 2026
- addedOutput schema / properties / results / items / properties / workshopId
```
Added value: +{
+  "pattern": "^[1-9]\\d{0,19}$",
+  "type": "string"
+}
```
- addedOutput schema / properties / results / items / properties / workshopUrl
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

Changed1 schema field changedOct 10, 2026

addedOutput schema / properties / results / items / properties / playFund

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "observedAt": {
+          "type": "string"
+        },
+        "state": {
+          "enum": [
+            "enabled",
+            "disabled",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "state",
+        "observedAt"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed3 schema fields changedOct 2, 2026

changedInput schema / properties / sort / enum

Previous value: -[
-  "players",
-  "playtime",
-  "change24h",
-  "created",
-  "updated",
-  "favorites",
-  "upvotes",
-  "score",
-  "servers"
-]New value: +[
+  "players",
+  "playtime7d",
+  "playtime",
+  "change24h",
+  "created",
+  "updated",
+  "favorites",
+  "upvotes",
+  "score",
+  "servers"
+]

addedOutput schema / properties / results / items / properties / weeklyPlaytimeBaselineAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / results / items / properties / weeklyPlaytimeSeconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / sort / enum

Previous value: -[
-  "players",
-  "change24h",
-  "created",
-  "updated",
-  "favorites",
-  "upvotes",
-  "score",
-  "servers"
-]New value: +[
+  "players",
+  "playtime",
+  "change24h",
+  "created",
+  "updated",
+  "favorites",
+  "upvotes",
+  "score",
+  "servers"
+]

addedOutput schema / properties / results / items / properties / totalSeconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed3 schema fields changedSep 4, 2026

addedInput schema / properties / jam

Added value: +{
+  "description": "Restrict games to an official s&box game jam.",
+  "enum": [
+    "three"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / jams

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "deadline": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "ident": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "ident",
+      "title",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "ident",
-  "title",
-  "summary",
-  "tags",
-  "canonicalUrl",
-  "markdownUrl"
-]New value: +[
+  "ident",
+  "title",
+  "summary",
+  "tags",
+  "jams",
+  "canonicalUrl",
+  "markdownUrl"
+]

First observedSep 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world behavior, so the safety profile is fully covered. The description contributes the 'public' scope and the nature of the surfaced data (live rankings, playtime windows, jam membership, source URLs), but no ranking/playtime definitions, freshness, or ordering defaults.

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?

A single dense sentence with the core predicate front-loaded and no filler. The trailing enumeration is long but each item is a concrete capability, so little is wasted.

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?

Because an output schema exists, the description needn't explain return values, yet that is nearly all it does — leaving the 5-parameter call semantics and any usage routing thin for a tool with 20% schema coverage. It is adequate but not comfortably complete.

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 only 20%, so the description must compensate, and it partially does: 'games, maps, or libraries' maps to the kind enum, 'official game-jam membership' maps to jam, and 'live rankings' / 'game playtime' hint at sort values. However it never mentions query, limit, the maximum of 25, or the 160-character query cap, and 'change24h' or 'servers' sorting is not reflected.

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?

States a specific verb and resource ('Find public s&box games, maps, or libraries') and enumerates the data it surfaces. It implicitly separates itself from siblings by scoping to packages rather than servers or organizations, but never names get_package or states how this search differs from the single-package fetch.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says when to search versus calling get_package directly, and no exclusions or prerequisites are given. Only the word 'public' hints at scope, and that must be inferred.

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

All s&box watch 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?