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

TableJSON Schema

Name	Required	Description	Default
`ident`	Yes

Output Schema

TableJSON 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 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 this a read-only, idempotent, non-destructive, non-open-world operation, so the safety profile is covered. The description adds minor value by noting the metadata is 'public' and the portfolio is 'bounded', hinting at result-size limits, but discloses nothing about auth needs, rate limits, or what happens with unknown idents.

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 that communicates verb, resource, and payload contents with no filler. Nothing could be cut without losing meaning.

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 one-parameter read tool with a full annotation set and an output schema (so return values need no prose), the description is nearly sufficient. The only meaningful gap is that the 'ident' argument's expected format and sourcing are never addressed.

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 sole parameter 'ident' carries only a regex pattern with no prose. The description does not explain that 'ident' is an organization slug/handle or how to obtain it, so it fails to compensate for the documentation gap.

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 ('Read one organization profile') and enumerates the payload shape (public metadata, aggregate activity, bounded package portfolio). It is clearly distinguishable from siblings like search_organizations by the 'one organization' framing, though it never names that 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?

The singular 'one organization' implies a direct-lookup use case versus the sibling search_organizations, but there is no explicit when-to-use/when-not-to-use statement and no mention of prerequisites such as needing a known identifier.

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?