Skip to main content
Glama

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

by ru.dokidepo
OverviewDiscussionsAdmin

Server Details

Read-only инструменты малого склада: назначение, ограничения и безопасный план первого дня.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
83.2% over 30 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool serves a clearly distinct purpose: widget retrieval, trial-day sequence, public tool details, publisher kit, and tool listing. No two tools overlap in function, and the descriptions make boundaries explicit.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (get_*, list_*), making the set predictable and easy to navigate. The mix of get_ and list_ is a standard convention for read operations.

Tool Count5/5

With 5 tools, the server is well-scoped for its informational purpose. Each tool adds value without redundancy, and the count is within the ideal range for a focused MCP server.

Completeness5/5

The server fully covers its advertised domain: listing tools, retrieving tool details, embedding widgets, providing a trial guide, and supplying a publisher kit. There are no obvious missing operations or dead ends.

Available Tools

5 tools
get_embed_widgetПолучить код бесплатного складского виджетаA
Read-onlyIdempotent
Inspect

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

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesstock-balance — приход, расход и остаток; markup-margin — наценка и маржа; purchase-list — количество к заказу; warehouse-bottleneck — диагностика узкого места; sku-generator — артикулы из названий или по порядку.

Output Schema

ParametersJSON Schema
NameRequiredDescription
safetyYes
widgetYes

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.

get_first_warehouse_dayПолучить безопасный план первого дняA
Read-onlyIdempotent
Inspect

Используйте, когда владелец малого склада хочет безопасно проверить ДокиДепо на одном учебном товаре до импорта каталога и приглашения команды. Без аргументов возвращает фиксированную последовательность: места → приёмка → размещение → отбор → упаковка → сверка. Не создаёт организацию, не меняет остатки и не принимает рабочие данные. Любое входное поле даёт JSON-RPC -32602 Invalid params.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
stepsYes
safetyYes
startUrlYes

TDQS

A4.8/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond the readOnly/idempotent/non-destructive annotations: it states the tool does not create an organization, does not change balances, does not accept working data, and any input field triggers a JSON-RPC -32602 error. This is valuable and does not contradict the 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?

The description is compact: it front-loads the use case, then clarifies behavior, side-effect safety, and error handling. Every sentence carries useful information with no filler.

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?

The tool has no parameters, an output schema, and complete annotations. The description covers when to use it, what it returns, what it does not do, and how it reacts to invalid input, so an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters and the schema already states that an empty object must be passed. The description goes further by explicitly warning that any input field produces JSON-RPC -32602 Invalid params, which adds practical guidance beyond the schema.

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 clearly specifies the tool's behavior: it returns a fixed sequence of warehouse steps for a safe first-day test in DokyDepo. It also names the intended use case, which distinguishes it from sibling tools like get_embed_widget 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 description explicitly states when to use the tool: when a small warehouse owner wants to safely test DokyDepo with one training item before importing a catalog and inviting a team. It does not mention alternatives or exclusion cases, so it stops short of a 5.

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

get_public_toolПолучить точную карточку инструментаA
Read-onlyIdempotent
Inspect

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

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesТочный неизменяемый идентификатор открытого инструмента ДокиДепо.

Output Schema

ParametersJSON Schema
NameRequiredDescription
toolYes
safetyYes

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses error behavior for unknown ids and extra fields, explicitly rejects non-id inputs, and clarifies the id must come from list_public_tools. It also summarizes the return content. This goes well beyond the annotations, which already mark the operation as read-only and idempotent.

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 compact and front-loaded, leading with the usage context and then explaining the return value and constraints. Every sentence adds actionable information without redundancy.

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 single-parameter, read-only lookup tool with a rich output schema and detailed annotations, the description covers when to use it, what it returns, how to pass the id, what not to pass, and what happens on invalid input. Nothing important is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents the id parameter with an enum and description, so the baseline is 3. The description adds meaningful semantics by stating that the id must come from list_public_tools and that unknown ids or extra fields produce JSON-RPC -32602 Invalid params.

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 clearly states the tool gets the exact card for a known public tool, naming the specific verb 'get', the resource 'tool card', and the precondition that the exact id is already known. It distinguishes itself from list_public_tools by explicitly saying to use it after that tool.

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 description provides clear usage context: use after list_public_tools when the exact id is known. It also states what inputs are not accepted (free text, URL, files, working data), but does not explicitly contrast with sibling tools like get_embed_widget or get_publisher_kit.

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

get_publisher_kitПолучить набор для редакции или сообществаA
Read-onlyIdempotent
Inspect

Используйте, когда редакции, сообществу или ИИ-агенту нужно подготовить публикацию о ДокиДепо без сочинения фактов и ссылок. Без аргументов возвращает фиксированные текст, ссылки, обложку, контакт и границы приватности. Не публикует материал и не принимает свободный текст, URL, файлы или данные аудитории. Любое входное поле даёт JSON-RPC -32602 Invalid params.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
kitYes
safetyYes

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral detail: it takes no arguments, returns fixed content, does not publish anything, and rejects any input field with JSON-RPC -32602. This fully discloses behavior beyond what the annotations provide.

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 sentences with no wasted words: the first gives the use case, the second defines the fixed output and no-argument contract, and the third defines the failure mode. The most important information is front-loaded.

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 no-argument, read-only tool with an output schema, the description covers the use context, the output composition, the input constraint, and the error behavior. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4, and the schema already documents that an empty object must be passed. The description adds practical value by warning that any attempted input field produces Invalid params, which is exactly the kind of guidance an agent benefits from.

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 names a specific use ('подготовить публикацию о ДокиДепо') and a specific deliverable: a fixed set of text, links, cover, contact, and privacy boundaries. It also clearly distinguishes itself from a publishing or content-accepting tool by stating it does not publish material and rejects free input.

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 explicitly states when to use the tool: when a publication needs to be prepared without inventing facts or links. It also gives clear when-not conditions: not for publishing, not for accepting free text, URLs, files, or audience data. It does not name a sibling alternative, but the exclusions are strong enough to prevent misrouting.

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

list_public_toolsНайти открытые инструменты складаA
Read-onlyIdempotent
Inspect

Используйте первым, когда нужно подобрать открытый складской инструмент по задаче. Необязательный category фильтрует каталог; без него возвращается all. Результат содержит только проверенные карточки и измеряемые ссылки ДокиДепо. Не выполняет складские операции и не принимает файлы, товары, пароли или коды. Лишнее поле или неизвестная категория дают JSON-RPC -32602 Invalid params.

ParametersJSON Schema
NameRequiredDescriptionDefault
categoryNoФиксированный фильтр: all — весь каталог; inventory — остатки, закупка и приёмка; labeling — этикетки, штрихкоды и адреса; pricing — цены и маржа; setup — запуск склада; publishing — встраиваемые виджеты; training — учебные материалы.all

Output Schema

ParametersJSON Schema
NameRequiredDescription
toolsYes
safetyYes

TDQS

A4.8/5.0
Behavior5/5

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

On top of annotations (readOnly, idempotent, non-destructive), the description adds meaningful behavior: it returns all when category is omitted, only verified cards and measureable DokiDepo links, and rejects extra fields or unknown categories with JSON-RPC -32602. This goes well beyond the annotations and schema.

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?

Every sentence earns its place: usage guidance is front-loaded, followed by parameter behavior, result guarantees, exclusions, and error behavior. It is compact, structured, and free of fluff.

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?

With rich annotations, a fully documented single parameter, an output schema present, and explicit guidance on usage, exclusions, defaults, and error cases, the description is complete for an agent to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the category enum descriptions are detailed. The description adds further value by explaining the default behavior (all), the optional nature of the parameter, and the exact error for unknown values or extra fields, which the schema alone does not fully convey.

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 clearly states the verb (list) and resource (public warehouse tools), and frames it as the first tool to use when selecting an open warehouse tool. It also distinguishes itself by explicitly stating it does not perform warehouse operations and does not accept files, goods, passwords, or codes, setting it apart from siblings.

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 description gives explicit guidance: 'Use first when you need to select an open warehouse tool by task.' It also excludes warehouse operations and files/goods/passwords/codes, implying alternatives for those uses. However, it does not name sibling tools explicitly, so the routing guidance is clear but not exhaustive.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedget_embed_widget4 fields changed
      • 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"
+]
    • Changedget_public_tool1 field changed
      • changedInput schema / properties / id / enum
        Previous value: -[
-  "stock-table",
-  "stock-balance-widget",
-  "batch-stock",
-  "purchase-list",
-  "purchase-list-widget",
-  "receiving-discrepancy-act",
-  "slow-moving-stock",
-  "expiry-control",
-  "inventory-turnover",
-  "packing-list",
-  "warehouse-bottleneck",
-  "warehouse-bottleneck-widget",
-  "price-tags",
-  "labels",
-  "barcode-scanner",
-  "compare-price-lists",
-  "table-diff",
-  "addresses",
-  "reconciliation",
-  "qr-code",
-  "markup-margin",
-  "markup-margin-widget",
-  "sku-generator",
-  "price-update-kit",
-  "returns-quarantine-writeoff",
-  "abc-xyz",
-  "safety-stock"
-]New value: +[
+  "stock-table",
+  "stock-balance-widget",
+  "batch-stock",
+  "purchase-list",
+  "purchase-list-widget",
+  "receiving-discrepancy-act",
+  "slow-moving-stock",
+  "expiry-control",
+  "inventory-turnover",
+  "packing-list",
+  "warehouse-bottleneck",
+  "warehouse-bottleneck-widget",
+  "price-tags",
+  "labels",
+  "barcode-scanner",
+  "compare-price-lists",
+  "table-diff",
+  "addresses",
+  "reconciliation",
+  "qr-code",
+  "markup-margin",
+  "markup-margin-widget",
+  "sku-generator",
+  "sku-generator-widget",
+  "price-update-kit",
+  "returns-quarantine-writeoff",
+  "abc-xyz",
+  "safety-stock"
+]
  2. 2 tool updates
    • Changedget_embed_widget4 fields changed
      • 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"
+]
    • Changedget_public_tool1 field changed
      • changedInput schema / properties / id / enum
        Previous value: -[
-  "stock-table",
-  "batch-stock",
-  "purchase-list",
-  "purchase-list-widget",
-  "receiving-discrepancy-act",
-  "slow-moving-stock",
-  "expiry-control",
-  "inventory-turnover",
-  "packing-list",
-  "warehouse-bottleneck",
-  "warehouse-bottleneck-widget",
-  "price-tags",
-  "labels",
-  "barcode-scanner",
-  "compare-price-lists",
-  "table-diff",
-  "addresses",
-  "reconciliation",
-  "qr-code",
-  "markup-margin",
-  "markup-margin-widget",
-  "sku-generator",
-  "price-update-kit",
-  "returns-quarantine-writeoff",
-  "abc-xyz",
-  "safety-stock"
-]New value: +[
+  "stock-table",
+  "stock-balance-widget",
+  "batch-stock",
+  "purchase-list",
+  "purchase-list-widget",
+  "receiving-discrepancy-act",
+  "slow-moving-stock",
+  "expiry-control",
+  "inventory-turnover",
+  "packing-list",
+  "warehouse-bottleneck",
+  "warehouse-bottleneck-widget",
+  "price-tags",
+  "labels",
+  "barcode-scanner",
+  "compare-price-lists",
+  "table-diff",
+  "addresses",
+  "reconciliation",
+  "qr-code",
+  "markup-margin",
+  "markup-margin-widget",
+  "sku-generator",
+  "price-update-kit",
+  "returns-quarantine-writeoff",
+  "abc-xyz",
+  "safety-stock"
+]
  3. 5 tool updates
    • Changedget_embed_widget2 fields changed
      • 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 — диагностика узкого места."
    • Changedget_first_warehouse_day1 field changed
      • addedInput schema / description
        Added value: +"Аргументы не принимаются; передайте пустой объект."
    • Changedget_public_tool2 fields changed
      • addedInput schema / description
        Added value: +"Передайте только точный id из результата list_public_tools."
      • addedInput schema / properties / id / description
        Added value: +"Точный неизменяемый идентификатор открытого инструмента ДокиДепо."
    • Changedget_publisher_kit1 field changed
      • addedInput schema / description
        Added value: +"Аргументы не принимаются; передайте пустой объект."
    • Changedlist_public_tools3 fields changed
      • addedInput schema / description
        Added value: +"Передайте только необязательный category. Пустой объект означает весь каталог."
      • addedInput schema / properties / category / default
        Added value: +"all"
      • changedInput schema / properties / category / description
        Previous value: -"all, inventory, labeling, pricing, setup, publishing или training"New value: +"Фиксированный фильтр: all — весь каталог; inventory — остатки, закупка и приёмка; labeling — этикетки, штрихкоды и адреса; pricing — цены и маржа; setup — запуск склада; publishing — встраиваемые виджеты; training — учебные материалы."
  4. 1 tool update
    • Changedget_public_tool1 field changed
      • changedInput schema / properties / id / enum
        Previous value: -[
-  "stock-table",
-  "batch-stock",
-  "purchase-list",
-  "purchase-list-widget",
-  "inventory-turnover",
-  "packing-list",
-  "warehouse-bottleneck",
-  "warehouse-bottleneck-widget",
-  "price-tags",
-  "labels",
-  "barcode-scanner",
-  "compare-price-lists",
-  "table-diff",
-  "addresses",
-  "reconciliation",
-  "qr-code",
-  "markup-margin",
-  "markup-margin-widget",
-  "sku-generator",
-  "price-update-kit",
-  "returns-quarantine-writeoff",
-  "abc-xyz",
-  "safety-stock"
-]New value: +[
+  "stock-table",
+  "batch-stock",
+  "purchase-list",
+  "purchase-list-widget",
+  "receiving-discrepancy-act",
+  "slow-moving-stock",
+  "expiry-control",
+  "inventory-turnover",
+  "packing-list",
+  "warehouse-bottleneck",
+  "warehouse-bottleneck-widget",
+  "price-tags",
+  "labels",
+  "barcode-scanner",
+  "compare-price-lists",
+  "table-diff",
+  "addresses",
+  "reconciliation",
+  "qr-code",
+  "markup-margin",
+  "markup-margin-widget",
+  "sku-generator",
+  "price-update-kit",
+  "returns-quarantine-writeoff",
+  "abc-xyz",
+  "safety-stock"
+]
  5. 5 tool updates
    • Changedget_embed_widget4 fields changed
      • 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"
+]
    • Changedget_first_warehouse_day1 field changed
      • addedOutput schema / additionalProperties
        Added value: +false
    • Changedget_public_tool2 fields changed
      • changedInput schema / properties / id / enum
        Previous value: -[
-  "stock-table",
-  "purchase-list",
-  "purchase-list-widget",
-  "inventory-turnover",
-  "warehouse-bottleneck",
-  "warehouse-bottleneck-widget",
-  "price-tags",
-  "labels",
-  "compare-price-lists",
-  "table-diff",
-  "addresses",
-  "reconciliation",
-  "qr-code",
-  "markup-margin",
-  "markup-margin-widget",
-  "sku-generator",
-  "price-update-kit"
-]New value: +[
+  "stock-table",
+  "batch-stock",
+  "purchase-list",
+  "purchase-list-widget",
+  "inventory-turnover",
+  "packing-list",
+  "warehouse-bottleneck",
+  "warehouse-bottleneck-widget",
+  "price-tags",
+  "labels",
+  "barcode-scanner",
+  "compare-price-lists",
+  "table-diff",
+  "addresses",
+  "reconciliation",
+  "qr-code",
+  "markup-margin",
+  "markup-margin-widget",
+  "sku-generator",
+  "price-update-kit",
+  "returns-quarantine-writeoff",
+  "abc-xyz",
+  "safety-stock"
+]
      • addedOutput schema / additionalProperties
        Added value: +false
    • Changedget_publisher_kit1 field changed
      • addedOutput schema / additionalProperties
        Added value: +false
    • Changedlist_public_tools1 field changed
      • addedOutput schema / additionalProperties
        Added value: +false
  6. 1 tool update
    • Addedget_publisher_kit
  7. 1 tool update
    • Addedget_embed_widget
  8. 1 tool update
    • Changedget_public_tool1 field changed
      • changedInput schema / properties / id / enum
        Previous value: -[
-  "stock-table",
-  "purchase-list",
-  "inventory-turnover",
-  "warehouse-bottleneck",
-  "warehouse-bottleneck-widget",
-  "price-tags",
-  "labels",
-  "compare-price-lists",
-  "table-diff",
-  "addresses",
-  "reconciliation",
-  "qr-code",
-  "markup-margin",
-  "markup-margin-widget",
-  "sku-generator",
-  "price-update-kit"
-]New value: +[
+  "stock-table",
+  "purchase-list",
+  "purchase-list-widget",
+  "inventory-turnover",
+  "warehouse-bottleneck",
+  "warehouse-bottleneck-widget",
+  "price-tags",
+  "labels",
+  "compare-price-lists",
+  "table-diff",
+  "addresses",
+  "reconciliation",
+  "qr-code",
+  "markup-margin",
+  "markup-margin-widget",
+  "sku-generator",
+  "price-update-kit"
+]
  9. 3 tool updates
    • First observedget_first_warehouse_day
    • First observedget_public_tool
    • First observedlist_public_tools

Related MCP Connectors

Related MCP Servers

  • mcp-bd-readonly

    noemartinezoptima
    F
    license
    C
    quality
    B
    maintenance
    Provides read-only access to a MySQL inventory and invoicing database through MCP tools, enabling safe SQL queries, table inspection, and financial reporting without any write capabilities.
    13
    -

  • Safe MCP Server

    Rajnish9444
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to read local business data and request database mutations, while requiring human approval before updates or deletions are executed. It provides read-only tools, approval workflows, and audit logging to prevent autonomous destructive changes.
    -

  • MCP Database Agent

    iarsingh
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables users to inspect databases through read-only tools that explain queries, sample rows, and list indexes, while refusing apply or delete operations.
    MIT

  • agentops-incident-commander

    SahanaReddy5
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides MCP-compatible safe read tools for incident investigation, enabling evidence collection and operational data access while keeping risky actions under human approval.
    MIT
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