Skip to main content
Glama
Sign In
OptimAI Search MCP

OptimAI Search MCP

Official
by OptimaiNetwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

optimai_cancel_search

Cancel a running or pending search by ID. Provide the search ID to stop processing; completed or already-cancelled searches are not affected.

Instructions

Cancel a running or pending search by its ID. Completed, failed, or already-cancelled searches cannot be cancelled.

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": {
      "id": "<id>"
    },
    "name": "optimai_cancel_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe search ID to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It provides the behavioral constraint that only running/pending searches can be cancelled, which is useful. However, it doesn't disclose what happens on success, failure, or whether cancellation is irreversible, leaving some gaps.

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?

The description is a single, direct sentence with no redundant words or fluff. It conveys the action and key constraint efficiently.

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 simple 1-parameter tool with no output schema, the description covers the action and key state constraint. It doesn't describe return values or error handling, but given the low complexity, this is adequate and mostly complete.

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 schema documents the single parameter 'id' fully ('The search ID to cancel'). The description adds no additional meaning beyond the schema, so the baseline score of 3 applies due to 100% schema coverage.

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?

The description uses a specific verb 'cancel' and identifies the resource as a search by ID. It clearly distinguishes from sibling tools like optimai_search, optimai_get_search, optimai_list_searches, and optimai_start_search.

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 states the tool applies to running or pending searches and explicitly lists non-cancellable states (completed, failed, already-cancelled), giving clear applicability boundaries. It doesn't mention alternatives but the context is sufficient for when to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools