Skip to main content
Glama
Sign In

Rebrickable

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Set

set
Read-onlyIdempotent

Fetch a single LEGO set by set_num (e.g. "75192-1") from Rebrickable. Returns set name, year, theme, part count, and image URL.

Input Schema

NameRequiredDescriptionDefault
set_numYes

Output Schema

NameRequiredDescriptionDefault
nameNoSet name
yearNoYear set was released
set_numNoSet number identifier
set_urlNoRebrickable URL for set
theme_idNoTheme ID
num_partsNoTotal number of parts
set_img_urlNoImage URL for set
num_minifigsNoTotal number of minifigures
last_modified_dtNoLast modification date

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "set_num": "75368-1"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "last_modified_dt": {
+      "description": "Last modification date",
+      "type": "string"
+    },
+    "name": {
+      "description": "Set name",
+      "type": "string"
+    },
+    "num_minifigs": {
+      "description": "Total number of minifigures",
+      "type": "number"
+    },
+    "num_parts": {
+      "description": "Total number of parts",
+      "type": "number"
+    },
+    "set_img_url": {
+      "description": "Image URL for set",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "set_num": {
+      "description": "Set number identifier",
+      "type": "string"
+    },
+    "set_url": {
+      "description": "Rebrickable URL for set",
+      "type": "string"
+    },
+    "theme_id": {
+      "description": "Theme ID",
+      "type": "number"
+    },
+    "year": {
+      "description": "Year set was released",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about the data source (Rebrickable) and specific return fields, which goes beyond annotations. It does not contradict annotations.

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 two sentences: the first states the action and parameter, the second lists return fields. No extraneous words. All information is front-loaded and relevant.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, clear output schema present), the description is complete. It explains the purpose, input format, and output fields adequately for an agent to invoke correctly.

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

Parameters5/5

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

The input schema has one required parameter (set_num) with 0% schema description coverage. The description compensates fully by providing an example ('75192-1') and clarifying the expected format. This adds significant meaning beyond the schema.

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 clearly states the tool fetches a single LEGO set by set_num, specifies the source (Rebrickable), and lists the returned fields (name, year, theme, part count, image URL). This distinguishes it from sibling tools like 'sets' (plural), 'set_parts', and 'set_minifigs'.

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 explains the primary use case (fetching a single set by set_num) but does not provide explicit guidance on when not to use it or mention alternatives. While sibling names imply distinctions, the description lacks direct usage boundaries.

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

All Rebrickable toolsInspect
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