Skip to main content
Glama

Leads of a search

list_leads
Read-onlyIdempotent

The people of a search by kind: fit («Подходят»: the leads, in their order), partial («Частично»: some requirement not proven, with what was assumed), miss («Не подходят», with the reason). Compact rows; paginate with offset/limit. get_lead gives one person's dossier with facts. [REST: GET /api/tasks/{id}/leads?kind=]

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>"
    },
    "name": "list_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNofit
limitNo
offsetNo
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds some behavioral value: rows are 'compact' (i.e., summaries, not dossiers), fit leads come in a meaningful order, and partial results carry assumption data. It does not describe pagination edge behavior or total counts, so it is useful but not rich.

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?

A single dense block that front-loads the resource and enumerates kinds immediately, followed by pagination mechanics and the sibling pointer. The parenthetical Russian labels add context rather than noise, though the sentence structure is somewhat tangled.

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?

With no output schema, the description carries the burden of describing returns and does so only briefly ('Compact rows'), without field names or what a row contains. For a 4-parameter list tool whose results drive downstream lead selection, that leaves a genuine gap.

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 only 25% (only task_id is documented in-schema), so the description must compensate and largely does: it defines the semantic of each kind enum value far beyond the bare enum, and states that offset/limit drive pagination. Defaults and the limit maximum of 100 are left to the schema, which 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 names a specific verb+resource ('The people of a search by kind') and spells out all three kind values with their meaning (fit = the leads in order, partial = requirement not proven plus what was assumed, miss = with the reason). It distinguishes itself from get_lead, which returns one person's dossier. The phrasing is slightly awkward, but an agent can tell exactly what it retrieves.

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 concrete usage mechanics ('paginate with offset/limit') and explicitly routes to a sibling: get_lead for a single person's dossier with facts. It does not state when-not to use this tool or what happens when a kind returns nothing, so it stops short of full 5-level guidance.

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