product_searchSearch fake DummyJSON products by keyword q. Returns matching products with name, price, brand, category, and rating. Supports limit and skip for pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | ||
| skip | No | ||
| limit | No |
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | Number of results skipped | |
| limit | No | Limit of results returned | |
| total | No | Total results found | |
| products | No | Search results |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "q": "laptop"
+ },
+ {
+ "limit": 5,
+ "q": "phone",
+ "skip": 0
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "limit": {
+ "description": "Limit of results returned",
+ "type": "number"
+ },
+ "products": {
+ "description": "Search results",
+ "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 results skipped",
+ "type": "number"
+ },
+ "total": {
+ "description": "Total results found",
+ "type": "number"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate safe read operation. Description adds return fields (name, price, brand, category, rating) and pagination behavior, providing useful context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words. Front-loaded with main action, then supplementary details. Excellent structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers purpose, required parameter, pagination, and return fields. Output schema exists so return details are delegated. Minor gaps: no mention of search behavior (partial match, case-sensitivity) or limitations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema coverage, description adds meaning by identifying `q` as keyword and explaining limit/skip for pagination. However, lacks details like default values, range, or case sensitivity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it searches fake DummyJSON products by keyword `q`. Distinguishes from sibling tools like 'products' (list all) and 'product' (single product by ID).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Describes keyword search and pagination support. Implicitly differentiates from listing all products, but no explicit when-to-use or when-not-to-use instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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 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.
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.
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.