Skip to main content
Glama

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

by ru.dokidepo
OverviewDiscussionsAdmin

Получить точную карточку инструмента

get_public_tool
Read-onlyIdempotent

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

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
safetyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema 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. Changed1 schema 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. Changed2 schema fields changed
    • addedInput schema / description
      Added value: +"Передайте только точный id из результата list_public_tools."
    • addedInput schema / properties / id / description
      Added value: +"Точный неизменяемый идентификатор открытого инструмента ДокиДепо."
  4. Changed1 schema 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. Changed2 schema 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
  6. Changed1 schema 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"
+]
  7. First observed

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.

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