ДокиДепо — открытые инструменты склада

Получить код бесплатного складского виджета

get_embed_widget

Read-onlyIdempotent

Используйте, когда редакции или сайту нужен готовый безопасный виджет: текущий остаток, расчёт наценки и маржи, количество к заказу, диагностика узкого места склада или генератор артикулов. Передайте один фиксированный id; сервер вернёт проверенный sandboxed iframe, страницу установки и ограничения. Не принимает HTML, URL или свободный текст. Неизвестный id или лишнее поле дают JSON-RPC -32602 Invalid params.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	stock-balance — приход, расход и остаток; markup-margin — наценка и маржа; purchase-list — количество к заказу; warehouse-bottleneck — диагностика узкого места; sku-generator — артикулы из названий или по порядку.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`safety`	Yes
`widget`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 20, 2026

changedInput schema / description

Previous value: -"Передайте только id одного из четырёх заранее опубликованных виджетов."New value: +"Передайте только id одного из пяти заранее опубликованных виджетов."

changedInput schema / properties / id / description

Previous value: -"stock-balance — приход, расход и остаток; markup-margin — наценка и маржа; purchase-list — количество к заказу; warehouse-bottleneck — диагностика узкого места."New value: +"stock-balance — приход, расход и остаток; markup-margin — наценка и маржа; purchase-list — количество к заказу; warehouse-bottleneck — диагностика узкого места; sku-generator — артикулы из названий или по порядку."

changedInput schema / properties / id / enum

Previous value: -[
-  "stock-balance",
-  "markup-margin",
-  "purchase-list",
-  "warehouse-bottleneck"
-]New value: +[
+  "stock-balance",
+  "sku-generator",
+  "markup-margin",
+  "purchase-list",
+  "warehouse-bottleneck"
+]

changedOutput schema / properties / widget / properties / id / enum

Previous value: -[
-  "stock-balance",
-  "markup-margin",
-  "purchase-list",
-  "warehouse-bottleneck"
-]New value: +[
+  "stock-balance",
+  "sku-generator",
+  "markup-margin",
+  "purchase-list",
+  "warehouse-bottleneck"
+]

Changed4 schema fields changedSep 20, 2026

changedInput schema / description

Previous value: -"Передайте только id одного из трёх заранее опубликованных виджетов."New value: +"Передайте только id одного из четырёх заранее опубликованных виджетов."

changedInput schema / properties / id / description

Previous value: -"markup-margin — наценка и маржа; purchase-list — количество к заказу; warehouse-bottleneck — диагностика узкого места."New value: +"stock-balance — приход, расход и остаток; markup-margin — наценка и маржа; purchase-list — количество к заказу; warehouse-bottleneck — диагностика узкого места."

changedInput schema / properties / id / enum

Previous value: -[
-  "markup-margin",
-  "purchase-list",
-  "warehouse-bottleneck"
-]New value: +[
+  "stock-balance",
+  "markup-margin",
+  "purchase-list",
+  "warehouse-bottleneck"
+]

changedOutput schema / properties / widget / properties / id / enum

Previous value: -[
-  "markup-margin",
-  "purchase-list",
-  "warehouse-bottleneck"
-]New value: +[
+  "stock-balance",
+  "markup-margin",
+  "purchase-list",
+  "warehouse-bottleneck"
+]

Changed2 schema fields changedSep 20, 2026

addedInput schema / description

Added value: +"Передайте только id одного из трёх заранее опубликованных виджетов."

changedInput schema / properties / id / description

Previous value: -"markup-margin, purchase-list или warehouse-bottleneck"New value: +"markup-margin — наценка и маржа; purchase-list — количество к заказу; warehouse-bottleneck — диагностика узкого места."

Changed4 schema fields changedSep 20, 2026

addedOutput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / widget / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / widget / properties

Added value: +{
+  "embedType": {
+    "enum": [
+      "sandboxed_iframe"
+    ],
+    "type": "string"
+  },
+  "html": {
+    "type": "string"
+  },
+  "id": {
+    "enum": [
+      "markup-margin",
+      "purchase-list",
+      "warehouse-bottleneck"
+    ],
+    "type": "string"
+  },
+  "installUrl": {
+    "type": "string"
+  },
+  "integrity": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "legacy": {
+    "type": "object"
+  },
+  "limitations": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "privacy": {
+    "type": "string"
+  },
+  "purpose": {
+    "type": "string"
+  },
+  "title": {
+    "type": "string"
+  },
+  "version": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / widget / required

Added value: +[
+  "id",
+  "title",
+  "purpose",
+  "installUrl",
+  "embedType",
+  "version",
+  "html",
+  "integrity",
+  "privacy",
+  "limitations",
+  "legacy"
+]

AddedSep 16, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that the server returns a sandboxed iframe, an installation page, and restrictions, and that unknown ids or extra fields produce a JSON-RPC Invalid params error. This meaningfully enriches the read-only, idempotent safety profile already declared by annotations.

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?

Three short sentences front-load the usage context, then cover expected output and error behavior with no filler. Every sentence earns its place.

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 one-parameter enum-based tool with an output schema and read-only annotations, the description is complete: it tells the agent when to use it, what to pass, what the server returns, and how failures are reported.

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% and the single id parameter already has an enum with per-value descriptions. The description adds only the general rule that exactly one fixed id is accepted, which is useful but does not materially extend the schema's parameter documentation.

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 names a specific verb and resource: obtaining ready-made embed-widget code, and lists concrete use cases such as stock balance, markup/margin, and SKU generation. It is clearly about widgets, but it never explicitly contrasts itself with siblings like get_public_tool or list_public_tools.

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?

The first sentence gives a clear when-to-use signal: 'when an editorial or site needs a ready-made safe widget'. It also states hard constraints (fixed id only, no HTML/URL/free text), but it does not name alternative tools or say when not to use this one.

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

All ДокиДепо — открытые инструменты склада 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?