Skip to main content
Glama

Новая заявка

create_lead

Завести заявку: человек и сделка одним запросом. Нужна почта, телефон или Telegram. Человек, который уже есть, не заводится второй раз; повторная заявка про то же ложится заметкой в открытую сделку. Заголовок Idempotency-Key защищает от двойной отправки.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailNo
phoneNo
commentNo
telegramNo
utm_termNo
course_idNo
utm_mediumNo
utm_sourceNo
utm_contentNo
utm_campaignNo
Idempotency-KeyNoКлюч повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / Idempotency-Key
      Added value: +{
      +  "description": "Ключ повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnly=false, destructive=false, idempotent=false); the description adds genuinely non-obvious behavior: existing people are not duplicated, and a repeat application for the same person is appended as a note to the open deal rather than creating a second record. The Idempotency-Key protection against double submission is also disclosed. It does not cover permissions, error cases, or what the call returns, which keeps it short of a 5.

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?

Four short sentences, front-loaded with what is created, then the contact requirement, then the duplicate semantics, then idempotency. Nothing is repeated and no sentence is expendable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter creation tool with no output schema and near-zero schema descriptions, the core semantics (creation, dedup, repeat-as-note, idempotency) are well covered. The UTM and course_id parameters and the shape of the successful response are left entirely unexplained, which is a meaningful gap at this parameter count.

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 only 8%, so the description must carry the burden, and it partially does by stating that email, phone, or Telegram is required — a validation rule the schema does not express since required is empty. The remaining nine parameters (utm_source/medium/campaign/term/content, course_id, name, comment) get no meaning from either source. Partial compensation, not full.

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 first sentence states a specific verb and compound resource: it files a lead, creating a person and a deal in one request. That compound behavior implicitly distinguishes it from the plain deal/course creation siblings, though no sibling is named. The scope is unambiguous enough that an agent knows what will exist after a successful call.

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

Usage Guidelines3/5

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

The description gives a precondition ('Нужна почта, телефон или Telegram') and explains the duplicate case, which is real usage guidance not present in the schema (required is empty). However, it never says when to prefer this over create_deal or how to handle an existing open deal deliberately. Usage is implied rather than routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources