Zavod Stanki CNC Catalog

Заявка менеджеру завода

submit_lead

Отправить заявку менеджеру завода: имя (обязательно) + телефон/e-mail, опционально модель и комментарий. API-ключ НЕ обязателен (публичный режим, лимит 3 заявки/час на IP; с ключом — без лимита). Заявка попадает в CRM и Telegram-чат менеджеров; подтверждай у клиента согласие на обработку контактов.

Input Schema

Name	Required	Description	Default
`name`	Yes
`email`	No
`phone`	No
`api_key`	No
`comment`	No
`machine_id`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`lead_id`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "lead_id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

While annotations cover the fundamental safety profile (readOnlyHint: false), the description adds key operational behaviors that are missing from structured data, such as the downstream effects (CRM and Telegram integration) and the rate limit logic based on API key usage.

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?

The description is highly efficient, front-loading the main action and then providing necessary operational detail (API limits and downstream delivery). It avoids fluff, though the single dense paragraph could be slightly broken up for maximal readability.

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 definition is highly complete for an invocation tool. It tells the agent exactly what data is needed, what success looks like (submission to CRM/Telegram), and what operational limits apply (rate limits/consent requirement).

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?

Since schema description coverage is 0%, the description must define parameters. It successfully defines required parameters (name + contact), optional parameters (model, comment), and the functional purpose of the API key parameter (access level/limits).

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 purpose is stated clearly and concisely in the title and description: 'Отправить заявку менеджеру завода' (Submit lead to factory manager). Given the sibling tools are mostly for retrieval or calculation, this action-oriented submission tool is easily distinguished.

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

Usage Guidelines5/5

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

It provides critical usage rules, such as the required fields (name + contact) and operational constraints (API key mode and rate limits). Most importantly, it mandates a compliance step: confirming client consent for data processing.

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

All Zavod Stanki CNC Catalog 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?