Skip to main content
Glama

Klinio

Stop a search

stop_search
Idempotent

Stops a queued or running search. The companies it already found stay.

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": {
      "search_id": "<search_id>"
    },
    "name": "stop_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_idYesThe search's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is partly covered. The description still adds real value by disclosing that previously found companies are preserved, which tells the agent the stop is partial-completion-safe rather than a data-wiping operation. It stops short of describing the response or error behavior for an unknown or finished search_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by the one consequence that matters. Every clause earns its place with no filler or repetition of the title.

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 one-parameter mutation-style control tool with no output schema and annotations covering safety, the description covers the essentials, including the fate of already-found data. Only minor gaps remain: what the call returns, and behavior on an already-finished or unknown search.

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?

The single parameter has 100% schema coverage with its own description ('The search's id.'), so the schema carries the semantics. The description adds nothing about where to obtain a valid search_id (e.g., from list_searches or get_search) or what an invalid id produces, so baseline 3 applies.

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 ('Stops') and resource ('a queued or running search'), and the scope qualifier narrows it precisely to queued/running states. Against siblings like get_search, list_searches, and get_results, the stop action is unmistakable, so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'queued or running' implies the applicable state and thus implicitly excludes searches that already finished, which is useful context. However, it never explicitly says what to do if the search is already complete or already stopped, and it does not route the agent to get_results for retrieving the retained companies.

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