Skip to main content
Glama

Dummyjson

by io.github.pipeworx-io

Products

products
Read-onlyIdempotent

Fetch a paginated list of fake products from DummyJSON. Supports limit, skip, and field selection via select. Returns product name, price, brand, category, thumbnail, and rating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNo
limitNo
selectNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of products skipped
limitNoLimit of products returned
totalNoTotal product count
productsNoList of products

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "skip": 0
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "description": "Limit of products returned",
+      "type": "number"
+    },
+    "products": {
+      "description": "List of products",
+      "items": {
+        "properties": {
+          "brand": {
+            "description": "Brand name",
+            "type": "string"
+          },
+          "category": {
+            "description": "Product category",
+            "type": "string"
+          },
+          "description": {
+            "description": "Product description",
+            "type": "string"
+          },
+          "discountPercentage": {
+            "description": "Discount percentage",
+            "type": "number"
+          },
+          "id": {
+            "description": "Product ID",
+            "type": "number"
+          },
+          "images": {
+            "description": "Product images",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "price": {
+            "description": "Product price",
+            "type": "number"
+          },
+          "rating": {
+            "description": "Product rating",
+            "type": "number"
+          },
+          "stock": {
+            "description": "Stock quantity",
+            "type": "number"
+          },
+          "thumbnail": {
+            "description": "Thumbnail URL",
+            "type": "string"
+          },
+          "title": {
+            "description": "Product title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "skip": {
+      "description": "Number of products skipped",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total product count",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark readOnlyHint, openWorldHint, idempotentHint as true. Description adds that data is fake from DummyJSON, which is a useful behavioral trait. However, no disclosure of rate limits or error handling beyond what annotations imply.

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?

Two sentences: first states purpose, second lists supported parameters and return fields. No wasted words, front-loaded with primary action.

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, return values are already documented. Description adds source (DummyJSON) and pagination details. Missing information like default pagination size or ordering is minor for a simple tool.

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

Parameters3/5

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

Schema description coverage is 0%, so description must compensate. It explains 'limit, skip, and field selection via `select`' but does not specify format for select (e.g., comma-separated) or default values. Partially compensates but leaves gaps.

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?

Description clearly states 'Fetch a paginated list of fake products from DummyJSON', specifying the verb (fetch), resource (list of products), and source (DummyJSON). It distinguishes from sibling tools like 'product' (single product) and 'product_search' (search) by emphasizing pagination and returning all products.

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?

No explicit guidance on when to use vs alternatives like 'product_search' or 'products_categories'. The description implies basic paginated listing, but does not explain when a user might prefer a search or category-based tool.

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

All Dummyjson toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools have overlapping purposes, e.g., multiple tools for data retrieval (ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile) that differ only in nuance, and the inclusion of both DummyJSON and Pipeworx tools creates confusion about which domain to use for what. Agents will struggle to select the correct tool.

Naming Consistency2/5

Naming conventions are mixed: Pipeworx tools use diverse patterns (verb_noun like 'validate_claim', noun like 'entity_profile', verb like 'forget'), while DummyJSON tools use simple nouns (posts, comments). No consistent pattern across the set.

Tool Count2/5

43 tools is excessive for a server named 'Dummyjson'. The majority are Pipeworx tools unrelated to fake data, making the set feel bloated and unfocused. The count is too large for the apparent scope.

Completeness3/5

For a fake data API, the set is incomplete: it only provides read operations (fetch, search) with no create, update, or delete capabilities. However, for the Pipeworx portion, the read coverage is extensive, so it's not severely lacking overall.

Resources