Skip to main content
Glama

Перевести сделку на этап

move_deal

Перевести сделку на другой этап той же воронки. Для отказа можно указать причину. Перевод пишется в ленту сделки с пометкой, что его сделал ключ API сотрудника. На этап «Оплачено» эта дверь не переводит, ответ 409: выигрыш считается продажей, его ставят оплата, кнопка в кабинете или дверь «Оплачено: открыть доступ».

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deal_id": "<deal_id>",
      "stage_id": "<stage_id>"
    },
    "name": "move_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
deal_idYes
stage_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive write, so the description's job is to add beyond that and it does: the move is recorded in the deal feed attributed to the employee's API key, and the Paid-stage attempt fails with a 409 rather than succeeding silently. Unstated is what happens on a redundant move (relevant given idempotentHint=false) and whether the client is notified.

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?

Purpose is front-loaded in the first sentence, followed by the optional parameter and then the hard restriction, so the most decision-relevant fact lands early. Phrasing is somewhat colloquial ('эта дверь не переводит') and the last sentence is dense, but no sentence is filler.

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 three-parameter mutation with no output schema, the definition covers the key hazard (the Paid stage and its 409) and the audit side effect, which is good. It still omits the success response shape, whether stages can be skipped or must be adjacent, and any permission prerequisite, leaving real gaps for an agent calling it blind.

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 0%, so the description must carry the parameter burden, and it only partly does. It explains reason (optional, used for a decline) and constrains stage_id to another stage of the same funnel, but deal_id and stage_id get no further semantics, and nothing says how a valid stage_id is discovered.

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 gives a precise verb plus resource plus scope: move a deal to another stage of the same funnel. It also draws a boundary against a different mechanism for the 'Paid' stage, though that alternative is described as a 'door' rather than named as an actual sibling tool, so the agent cannot map it to a callable name.

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?

There is an explicit when-not: this tool must not be used to reach the 'Paid' stage, and the description explains why (a win is a sale, set by payment, a dashboard button, or the 'Paid: grant access' door) and what to expect (409). It also indicates when to fill the reason field (for a decline). The gap is that the recommended alternative is not identified by a tool name the agent can actually invoke.

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