Caspar Manufaktur Materialberater

list_materials

Read-only

List selected wallpaper materials with surface, width and primary use cases.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_materials"
  }
}

Input Schema

Name	Required	Description
`id`	No	Optional. Return only the material with this id.
`limit`	No	Optional. Page size, default 50.
`offset`	No	Optional. Number of materials to skip, default 0.
`priority`	No	Optional. Filter by priority tag, e.g. brandschutz, robust, effekt, nachhaltig, feuchtraum.

Output Schema

Name	Required	Description
`items`	Yes
`limit`	Yes
`total`	Yes	Number of matching materials before paging
`offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "datasheet_url": {
+            "format": "uri",
+            "type": "string"
+          },
+          "id": {
+            "description": "Material key",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "priority": {
+            "description": "Priority tags, e.g. brandschutz, robust",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "processing_guide_url": {
+            "format": "uri",
+            "type": "string"
+          },
+          "surface": {
+            "type": "string"
+          },
+          "weight_g_m2": {
+            "description": "Base weight in g/m²",
+            "type": "number"
+          },
+          "weight_note": {
+            "type": "string"
+          },
+          "width_cm": {
+            "description": "Panel width in cm (maximum print width for Welltouch XL)",
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "surface",
+          "width_cm",
+          "weight_g_m2"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "integer"
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "total": {
+      "description": "Number of matching materials before paging",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "items",
+    "total",
+    "offset",
+    "limit"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedOct 12, 2026

addedInput schema / properties / id

Added value: +{
+  "description": "Optional. Return only the material with this id.",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Optional. Page size, default 50.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Optional. Number of materials to skip, default 0.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / priority

Added value: +{
+  "description": "Optional. Filter by priority tag, e.g. brandschutz, robust, effekt, nachhaltig, feuchtraum.",
+  "type": "string"
+}

First observedSep 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add context. It does not disclose pagination behavior despite having limit/offset, nor what "selected" means, but it does hint at the returned fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is tight, but the brevity comes at the cost of omitting routing guidance rather than through efficient compression of useful content.

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

Completeness3/5

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

All four parameters are optional, an output schema exists, and annotations are present, so the definition is not dangerously incomplete. Still, a list tool with a filter parameter and a close sibling deserves at least a line on filtering vs. recommending.

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 100%, so the schema fully documents id, limit, offset and priority, including example priority tags. The description adds no meaning beyond that, which is the expected baseline when the schema carries the burden.

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 ("List ... wallpaper materials") plus the returned attributes (surface, width, primary use cases), so an agent knows this is a catalog read. It does not differentiate from the nearest sibling, recommend_material, and the word "selected" is left unexplained.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no mention of when not to use it. The only plausible alternative in the sibling set, recommend_material, is never referenced, so an agent must guess which of the two answers a material-discovery question.

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

All Caspar Manufaktur Materialberater 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?