s&box watch

Search s&box packages

search_packages

Read-onlyIdempotent

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

Input Schema

TableJSON 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

TableJSON 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.

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds useful behavioral context about the result content (live rankings, game-jam membership, canonical URLs), which goes beyond annotations. It does not disclose pagination or rate limits, but annotations make it a safe read operation, so the added context justifies a 4.

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?

The description is a single sentence that front-loads the verb and resource, with no filler. It efficiently communicates the core purpose and key distinguishing features.

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?

An output schema exists, so return format is covered. However, the description lacks guidance on when to use the tool vs alternatives and does not clarify the semantics of sort, limit, or query. For a search tool with five parameters, this is a moderate gap, making it minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only 'jam' has a description). The description hints at 'kind' (games, maps, libraries) and 'jam' (game-jam) but does not explain 'sort', 'limit', or 'query'. With low schema coverage, the description should compensate but only partially does, leaving agents uncertain about key parameters.

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 states a specific verb ('Find') and a specific resource ('public s&box games, maps, or libraries'), and highlights distinct features (live rankings, official game-jam membership, canonical source URLs). This clearly differentiates it from sibling tools like search_servers (which searches servers) and get_package (which likely retrieves a specific package).

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

Usage Guidelines3/5

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

The description implies this tool is for searching packages, but it does not explicitly state when to use it versus alternatives like get_package or search_servers. There are no exclusion conditions or scenarios where another tool should be preferred, leaving the agent to infer usage.

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?