Skip to main content
Glama

Price of facts on request / move to fit

quote_facts_on_request

After a search: the price in credits of finding facts for chosen partial people and moving them to fit («перевести в подходящие», promote=true), or facts only (promote=false). Free, changes nothing; the answer's credits is the confirm_credits of start_facts_on_request, skipped the people it does not take and why. [REST: POST /api/tasks/{id}/manual/quote]

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": "quote_facts_on_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidsYesPerson ids (cid) from list_leads.
promoteNo
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

B3.4/5.0
Behavior1/5

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

The description says the operation is 'Free, changes nothing', which directly conflicts with the annotation readOnlyHint=false indicating the tool is not read-only. It also says changes nothing while idempotentHint=false, reinforcing the inconsistency. Although the description adds useful return details about credits and skipped people, the contradiction with the supplied annotations is serious.

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 front-loaded with the core action and mode distinction, then adds return-value and side-effect context. It is dense but mostly earns its place. The Russian parenthetical and REST endpoint are extra but not excessive.

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 three-parameter tool with no output schema, the description covers the key behavior: cost, side effects, promote modes, and the meaning of returned credits and skipped entries. It does not fully resolve the ambiguous 'partial people' wording, and the stated no-change behavior conflicts with annotations. Still, it is substantially complete for invocation.

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 67%, and the description compensates for the undocumented promote parameter by explaining promote=true as moving people to fit and promote=false as facts only. It also gives context for cids and task_id by tying them to chosen people and an existing search. The schema already documents cids and task_id formats, so the description appropriately adds meaning beyond it.

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 specific action: quoting the credit price for finding facts for selected people, with two modes controlled by promote. It is distinguishable from the sibling start_facts_on_request because it describes pricing rather than starting the task. The phrase 'chosen partial people' is somewhat jargon-heavy, but the overall purpose is clear.

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 clear timing context with 'After a search' and explains the two modes: promote=true for moving people to fit and promote=false for facts only. It also ties the returned credits to start_facts_on_request, implying this is a preview before confirmation. It does not explicitly state when not to use it, but the context is strong.

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