Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Маркет сценариев

market_list
Read-onlyIdempotent

Search the ready-made scenario catalog by title, description, category, platform, source, and AI or knowledge needs; filter by case to check install status before market_install.

Instructions

Каталог готовых сценариев: от проекта и опубликованные другими делами. Поиск по названию и описанию, отбор по разделу, платформе, источнику и потребности в ИИ или базе знаний. С параметром case у каждой публикации видно, стоит ли она уже в этом деле и не отстала ли от свежей версии. Установка — market_install.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
mineNoТолько публикации этого дела — то, что выложили сами.
sortNopopular — по установкам (по умолчанию), new — свежие, likes — по лайкам.
limitNoСколько записей вернуть, максимум 100. По умолчанию 30.
queryNoЧто искать в названии и описании.
scopeNodialog — сценарии для личной переписки, community — для сообществ.
offsetNoСколько записей пропустить.
sourceNoproject — от проекта operbots, community — опубликованные делами.
categoryNoРаздел маркета.
needs_aiNoЕсть ли в сценарии узлы с ИИ.
platformNoТолько сценарии, годные для этой платформы.
origin_case_idNoИдентификатор дела-источника: только его публичные публикации.
needs_knowledgeNoНужна ли сценарию база знаний.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / origin_case_id
      Added value: +{
+  "description": "Идентификатор дела-источника: только его публичные публикации.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.17
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "dialog — сценарии для личной переписки, community — для сообществ.",
+  "enum": [
+    "dialog",
+    "community"
+  ],
+  "type": "string"
+}
  3. Addedv0.1.16

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely behavioral context beyond them: that supplying case annotates each listing with installation status and version-staleness. This is meaningful added value, though return format is not described.

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?

Four sentences, front-loaded with the purpose, then search/filter capabilities, the case-parameter behavior, and the install pointer. Dense but each sentence earns its place; minor compression possible.

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?

For a 13-parameter read-only list tool with no output schema and full schema coverage, the description is complete enough to call correctly and understand the case-driven enrichment. It omits pagination/return-shape guidance, but that is not essential here.

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?

Schema coverage is 100%, so the baseline is 3. The description rises above it by explaining the semantic effect of the case parameter (install status and version drift per publication) and summarizing the filter dimensions (section, platform, source, AI/knowledge needs, title/description search).

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?

States a specific verb+resource: a catalog of ready-made scenarios from the project and from other cases, with search and filtering. It clearly distinguishes itself from market_install (installation), market_get, and market_publish without requiring the reader to open other schemas.

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?

Explicitly routes installation to market_install and explains that the case parameter surfaces whether a publication is already installed and whether it lags the current version. It gives clear usage context but does not state when to prefer market_get over market_list or any exclusion conditions.

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

Deploy Server

Other Tools