Skip to main content
Glama

Move fit leads to partial

demote_lead

After a search: moves chosen fit people to partial («в частично подходящие»), e.g. the user disagrees with the verdict. Free, at once. [REST: POST /api/tasks/{id}/demote]

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": {
      "task_id": "<task_id>",
      "cids": "<cids>"
    },
    "name": "demote_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidsYesPerson ids (cid) from list_leads.
task_idYesThe search id (task id), e.g. from list_searches or create_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds cost and timing context ('Free, at once'), which is genuinely beyond the annotations. However, it does not address the non-idempotent flag (what happens if the same cids are demoted twice) nor whether the change is reversible, so the added behavioral value is moderate.

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?

Short, front-loaded, and the essential precondition ('After a search') leads the sentence. The trailing REST endpoint tag and the parenthetical Russian gloss are useful but slightly cluttering; nothing is wasted overall.

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?

With only two parameters, full schema documentation, and annotations covering the safety profile, the description supplies the remaining essentials: the trigger, the semantic effect, and the cost/latency. Edge behavior (invalid cids, repeated demotion, partial failure across up to 300 ids) is left unstated, but nothing critical to a correct call is missing.

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 100% — task_id and cids are both documented in-schema, including their source tools (list_searches/create_search, list_leads). The description only implies the cids must be currently-fit people from a given search, adding marginal meaning. Baseline 3 is appropriate.

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 description states a precise verb and effect ('moves chosen fit people to partial'), including the Russian gloss of the target state and a sample motive (the user disagrees with the verdict). That makes the state transition unambiguous. It does not explicitly contrast itself with any sibling tool, which keeps it just short of a 5.

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?

It gives a concrete trigger: use it after a search when the user disagrees with a 'fit' verdict. That is clear operational context. There is no explicit when-not guidance or named alternative (e.g., what to do for non-fit leads), so it stops at 4 rather than 5.

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