s&box watch

Get an s&box package

get_package

Read-onlyIdempotent

Read compact details, official game-jam membership, recent publisher updates, and live-server links for one public s&box package.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No		game
`ident`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jams`	Yes
`tags`	Yes
`ident`	Yes
`score`	No
`title`	Yes
`created`	No
`creator`	No
`sboxUrl`	No
`summary`	Yes
`updated`	No
`updates`	Yes
`upvotes`	No
`fileSize`	No
`downvotes`	No
`favorites`	No
`generation`	Yes
`playersNow`	No
`supportsVr`	No
`totalUsers`	No
`description`	Yes
`generatedAt`	Yes
`liveServers`	Yes
`markdownUrl`	Yes
`momentum24h`	No
`canonicalUrl`	Yes
`totalSeconds`	No
`updatesTotal`	Yes
`contentNotice`	Yes
`totalSessions`	No
`playersPeak24h`	No
`supportsController`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 4, 2026

addedOutput schema / 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 / required

Previous value: -[
-  "ident",
-  "title",
-  "summary",
-  "tags",
-  "canonicalUrl",
-  "markdownUrl",
-  "generation",
-  "generatedAt",
-  "contentNotice",
-  "description",
-  "updatesTotal",
-  "updates",
-  "liveServers"
-]New value: +[
+  "ident",
+  "title",
+  "summary",
+  "tags",
+  "jams",
+  "canonicalUrl",
+  "markdownUrl",
+  "generation",
+  "generatedAt",
+  "contentNotice",
+  "description",
+  "updatesTotal",
+  "updates",
+  "liveServers"
+]

First observedSep 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description doesn't need to restate safety. It adds meaningful behavioral scope: public-only packages, compact details rather than full package data, and live-server links, which go beyond what annotations and schema alone convey.

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?

One dense, front-loaded sentence with no filler or repetition of structured fields. Every phrase adds information about scope or returned content.

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

Completeness4/5

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

For a read-only tool with two parameters and an output schema, the description covers the main data categories and the public-only restriction. It doesn't explicitly address parameter format or failure cases, but the schema fills most of that gap; a brief usage-routing note would make it fully 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 0%, and the description does not explain the 'ident' or 'kind' parameters. The agent must infer the author.package identifier format and the filtering role of 'kind' entirely from the schema. The description provides only a loose hint that the resource is a package.

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 opens with a specific verb ('Read') and names a precise resource ('one public s&box package'), then lists the exact data categories returned. The 'one public' scope clearly differentiates it from search_packages without needing to open 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 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 fetching a known, single public package, but it never explicitly says when to prefer it over search_packages or the other sibling tools. Usage context is present but left to inference rather than stated.

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?