Camden Tools

List brands

list_brands

Read-only

Brands sold by Camden Tools (DeWalt, Makita, Milwaukee, Bosch, Stanley …). Without a query returns the popular brands; with a query searches brand names.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, starting at 1.
`sort`	No	Sort order: price_low, price_high, name_asc, name_desc or newest. Omit for the default (most popular) order.
`query`	No	Brand name search text.
`per_page`	No	Results per page: 15, 30, 50 or 100 (default 15).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`brands`	Yes
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "brands": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "number"
+          },
+          "logo": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "product_count": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "slug",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "last_page": {
+              "type": "number"
+            },
+            "page": {
+              "type": "number"
+            },
+            "per_page": {
+              "type": "number"
+            },
+            "total": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "page",
+            "per_page",
+            "total",
+            "last_page"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "brands",
+    "pagination"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only and non-destructive behavior, and the description adds value by revealing the conditional behavior: no query returns popular brands, while a query searches brand names. This goes beyond the annotation signals without contradicting them.

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 concise sentences with no filler. The resource and scope are front-loaded, and every clause contributes useful behavioral information.

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?

For a simple list tool with no required parameters, a high-coverage schema, an output schema, and safety annotations, the description is complete. It covers the main call patterns and the scope of the brand catalog, leaving no critical behavioral gaps.

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 coverage is 100%, so the schema already documents all four parameters. The description adds modest context around the query parameter (searches brand names) and the default popular-brand behavior, but page, sort, and per_page semantics remain entirely schema-defined.

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 identifies the exact resource (Camden Tools' brands) and gives concrete examples (DeWalt, Makita, Milwaukee). It also distinguishes the tool from sibling product/category tools by focusing on the brand catalog and by stating the query/no-query behaviors.

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 when to include or omit the query parameter, which is useful internal guidance. However, it does not explicitly compare this tool with siblings such as get_brand_products, list_products, or search_products, so selection guidance is implied rather than stated.

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

All Camden Tools 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?