Ręczniki Haftowane

fetch

Read-onlyIdempotent

Pobiera pełną treść publicznego produktu po id zwróconym przez search, wraz z tytułem i URL-em do cytowania.

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description
`id`	No
`url`	No
`text`	No
`error`	No	Tylko przy isError: { code, message, ... }
`title`	No
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / error / properties / details

Added value: +{
+  "description": "Powody odrzucenia kolorów (invalid_input z get_creator_link)",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "allowed_option_ids": {
+        "description": "Aktywne option_id typu slotu; wybierz jedno z nich",
+        "items": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "type": "array"
+      },
+      "asset_type_id": {
+        "anyOf": [
+          {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "field": {
+        "description": "Np. slots[0].option_id",
+        "type": "string"
+      },
+      "given": {
+        "description": "Podany option_id",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "message": {
+        "type": "string"
+      },
+      "reason": {
+        "enum": [
+          "unknown_option",
+          "inactive",
+          "type_mismatch",
+          "slot_out_of_range",
+          "no_color_choice"
+        ],
+        "type": "string"
+      },
+      "slot_position": {
+        "description": "Pozycja slotu 1-based",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "field",
+      "slot_position",
+      "asset_type_id",
+      "reason",
+      "given",
+      "allowed_option_ids",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / error / properties / hint

Added value: +{
+  "description": "Wskazówka naprawy (invalid_input), np. lista nieznanych tagów",
+  "type": "string"
+}

Changed4 schema fields changedOct 23, 2026

addedOutput schema / properties / error / properties / cause

Added value: +{
+  "pattern": "^(timeout|http_\\d{3}|matomo_error|invalid_response|not_configured|matomo_method_unavailable)$",
+  "type": "string"
+}

changedOutput schema / properties / error / properties / code / enum

Previous value: -[
-  "invalid_input",
-  "not_found",
-  "shop_unavailable"
-]New value: +[
+  "invalid_input",
+  "not_found",
+  "shop_unavailable",
+  "analytics_unavailable"
+]

changedOutput schema / properties / error / properties / retry_after_seconds / description

Previous value: -"Po ilu sekundach ponowić żądanie (shop_unavailable)"New value: +"Po ilu sekundach ponowić żądanie (niedostępność źródła)"

addedOutput schema / properties / error / properties / status

Added value: +{
+  "description": "Status błędu analityki; report_unavailable oznacza brak raportu/konfiguracji",
+  "enum": [
+    "report_unavailable",
+    "error"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": false,
+  "description": "Tylko przy isError: { code, message, ... }",
+  "properties": {
+    "code": {
+      "enum": [
+        "invalid_input",
+        "not_found",
+        "shop_unavailable"
+      ],
+      "type": "string"
+    },
+    "correlation_id": {
+      "description": "Identyfikator do zgłoszenia problemu (shop_unavailable)",
+      "type": "string"
+    },
+    "fields": {
+      "description": "Nazwy błędnych parametrów (invalid_input)",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "retry_after_seconds": {
+      "description": "Po ilu sekundach ponowić żądanie (shop_unavailable)",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "id",
-  "title",
-  "text",
-  "url"
-]

Changed1 schema field changedOct 20, 2026
- removedInput schema / properties / id / minLength
```
Removed value: -1
```
First observedOct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and a closed-world scope, so the safety profile is covered. The description adds a real constraint that only public products are retrievable and hints at return content (title and citation URL), but says nothing about permissions or failure behavior for missing/private ids.

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 appropriately sized for a one-parameter fetch tool and puts the retrieval purpose first.

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 present, return structure need not be explained, and annotations cover the safety profile. Given the tool's simplicity, the description plus structured data is nearly complete; only the missing id format is a small gap.

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% for the single `id` parameter, so the description must carry the burden. It does explain the id's origin (returned by `search`), which is useful, but it omits format and the maxLength of 100 that the schema imposes.

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?

The description states a specific verb and resource: it fetches the full content of a public product by id, together with its title and citation URL. It also names the sibling `search` as the source of the id, which helps distinguish it from the search/list tools, though it doesn't differentiate itself explicitly from `search_products`.

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

Usage Guidelines4/5

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

It tells the agent the precondition clearly: use the id returned by `search`. The usage context (fetch details after searching) is therefore clear, but there are no explicit when-not-use cases or comparisons with the other sibling tools such as `get_product_options`.

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

All Ręczniki Haftowane 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?