s&box watch

Get an s&box organization

get_organization

Read-onlyIdempotent

Read one organization profile with public metadata, aggregate activity, and a bounded package portfolio.

Input Schema

Name	Required	Description	Default
`ident`	Yes

Output Schema

Name	Required	Description	Default
`stats`	Yes
`apiUrl`	Yes
`generation`	Yes
`portfolios`	Yes
`generatedAt`	Yes
`markdownUrl`	Yes
`analyticsUrl`	Yes
`canonicalUrl`	Yes
`organization`	Yes
`contentNotice`	Yes
`analyticsApiUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed1 schema field changedOct 10, 2026

addedOutput schema / properties / portfolios / items / properties / packages / 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"
+    }
+  ]
+}

Changed2 schema fields changedOct 2, 2026
- addedOutput schema / properties / portfolios / items / properties / packages / items / properties / weeklyPlaytimeBaselineAt
```
Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
```
- addedOutput schema / properties / portfolios / items / properties / packages / items / properties / weeklyPlaytimeSeconds
```
Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
```
Changed1 schema field changedOct 1, 2026
- addedOutput schema / properties / portfolios / items / properties / packages / items / properties / totalSeconds
```
Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
```
AddedSep 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the shape of the payload (metadata, aggregate activity, bounded portfolio), which is useful framing, but says nothing about error behavior for a missing/unknown ident or the "bounded" limit.

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?

A single front-loaded sentence with no filler; the verb and scope lead, and every clause earns its place by delimiting the 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?

With an output schema present, return values need not be explained, and the annotations cover the safety profile, so the description is close to sufficient. The remaining gap is the meaning and expected form of the required `ident` parameter.

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%, so the description carries the burden of explaining `ident` — and it never mentions it. An agent gets only the pattern constraint from the schema and no guidance that ident is the org slug/handle, how it relates to names returned by search_organizations, or case sensitivity.

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 ("Read") and resource ("one organization profile") plus the payload scope (public metadata, aggregate activity, bounded package portfolio). The singular "one" implicitly contrasts with the sibling search_organizations, though it never names the alternative explicitly.

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?

Usage is implied by "one organization" versus the plural search_organizations sibling: retrieve a single known org rather than search. There is no explicit statement of when to use this versus search_organizations, no prerequisites, and no exclusions.

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?