Skip to main content
Glama

Find more leads (spends credits)

continue_search

«Продолжить поиск»: a finished or stopped search goes on for more more leads with the same requirements (no new brief). SPENDS CREDITS: quote_search(leads=more) first, show the price, and after the user's yes pass its credits_high as confirm_credits. Returns at once; poll get_search. [REST: POST /api/tasks/{id}/more]

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>",
      "more": "<more>",
      "confirm_credits": "<confirm_credits>"
    },
    "name": "continue_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
moreYes
task_idYesThe search id (task id), e.g. from list_searches or create_search.
stop_at_targetNo
confirm_creditsYesThe price in credits the matching quote returned, shown to the user and confirmed by them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-idempotent, non-destructive write. The description adds the crucial behavior annotations cannot express: it SPENDS CREDITS, requires a priced quote plus user confirmation, and returns immediately so results must be polled via get_search.

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?

Front-loads the resource, then the credit warning, then the required call sequence, then the async note — a sensible order with little filler. The Cyrillic label and the bracketed REST endpoint are minor overhead that an agent doesn't strictly need.

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?

For a four-parameter mutating, credit-spending, asynchronous tool, the description covers precondition, cost gate, confirmation value, and follow-up polling. No output schema exists and none is needed given the get_search polling instruction.

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?

With 50% schema coverage the description does real work: it explains `more` as the count of additional leads and `confirm_credits` as the credits_high value from the matching quote, and implies task_id is the search id. `stop_at_target`, however, is never explained in either place.

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?

States a specific verb and resource: it extends a finished or stopped search for `more` additional leads under the same requirements. The parenthetical '(no new brief)' distinguishes it from create_search/run_search without needing schemas.

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?

Gives an explicit precondition (the search must be finished or stopped) and a full routing rule: call quote_search(leads=more) first, show the price, get user consent, then pass its credits_high as confirm_credits. No inference required about when to use a sibling.

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