Skip to main content
Glama
Sign In
OptimAI Search MCP

OptimAI Search MCP

Official
by OptimaiNetwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

optimai_get_search

Retrieve the current status and results of an ongoing or completed search by its ID.

Instructions

Retrieve the current status and result of a previously created search by its ID. Useful for checking on a search that was started earlier or is still in progress.

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_get_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe search ID returned by optimai_search or optimai_list_searches

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 provided, the description carries the transparency burden. It communicates a read-only nature via 'retrieve' and notes it returns 'status and result', but does not explicitly state non-destructive behavior, error handling, or whether the response is immediate. This is minimal but adequate for a simple retrieval tool.

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 sentences, front-loaded with the primary purpose, and no wasted words. The second sentence adds practical usage context, earning a perfect score.

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 single-parameter, no-output-schema tool, the description is sufficiently complete. It explains what the tool does and when to use it, and hints at polling behavior for in-progress searches. It does not specify response format or error scenarios, but these are less critical given the simple scope.

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?

Schema coverage is 100%, and the schema already describes the 'id' parameter as the search ID returned by optimai_search or optimai_list_searches. The description's phrase 'by its ID' adds no new semantic detail, so the baseline of 3 is appropriate.

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 clearly states the tool retrieves the current status and result of a previously created search by ID. It uses specific verbs ('retrieve') and identifies the resource ('search'), effectively distinguishing it from sibling tools like optimai_search, optimai_list_searches, and optimai_cancel_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?

The description provides clear context: it's useful for checking a search that was started earlier or is still in progress. It implies when to use this tool over listing all searches, though it does not explicitly name alternatives or exclusions.

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