Skip to main content
Glama

My searches

list_searches
Read-onlyIdempotent

The user's searches («Мои поиски»), newest first: id, title, status, leads / partial found, target, credits charged, progress of a running one. [REST: GET /api/tasks]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_searches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real behavior: results are scoped to the current user, sorted newest first, and each record carries id, title, status, lead counts, target, credits charged and live progress — enough to know what a call yields without an output schema. It says nothing about what happens past the default page of 25 or how totals are reported, which is the remaining gap.

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 front-loaded sentence that immediately answers 'what comes back', with the REST endpoint appended as a compact reference. The field list is dense but each item earns its place; only the compressed phrase 'leads / partial found' is ambiguous enough to cost a point.

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?

Because there is no output schema, the enumerated return fields are genuinely necessary and well chosen. But with 0% parameter coverage and an enum filter, the definition leaves an agent unable to use the status or pagination arguments meaningfully, which is a notable omission for an otherwise simple list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and three parameters exist, so the description must compensate — and it does not. It mentions 'status' only as a returned field, never as a filter, and never explains the enum values (compiling, ready, queued, running, paused, asking, done, stopped, failed) or how limit/offset pagination should be used.

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 resource (the user's searches, with the Russian UI label «Мои поиски») and even maps it to GET /api/tasks, so an agent knows exactly what it returns. It lacks an explicit verb and does not distinguish itself from search-related siblings like create_search, diagnose_search or export_search, which keeps it 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says to call this to discover search ids before invoking control_search/delete_search, and no exclusions or alternatives are named. The status filter is not described as a way to narrow the list, so an agent has to infer its purpose from the schema alone.

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