AnySearch

batch_search

Read-onlyDestructive

This is Anysearch's parallel search tool. Parallel search — run multiple Anysearch queries in a single call. Prefer this over multiple sequential calls when you have 2–5 queries. Saves context space and returns all results at once. Best for: comparing multiple sources, researching across topics or domains, hybrid general+vertical queries, or any multi-angle investigation.

When to use

Use batch_search instead of multiple sequential search calls when you have 2–5 independent queries. 🏆 PRIMARY use case: After get_sub_domains(domains=[...]) returns sub_domains across multiple domains, use batch_search to send one query per sub_domain in parallel. This is more efficient than sequential per-domain search calls. Also useful for ambiguous / fuzzy queries within a single domain: after get_sub_domains, use batch_search to explore multiple sub_domains in parallel.

Constraints

Maximum 5 queries per call
Each query item follows the search tool parameter structure (query is required; domain, sub_domain, sub_domain_params are optional. For general queries, omit all domain fields. For vertical queries, domain + sub_domain + sub_domain_params MUST come from get_sub_domains(domain=) output — same rules as the search tool)
Queries run in parallel; a single query failure does not block others
REQUIRED PARAMS: Same rule as search — when a required param from get_sub_domains is not applicable, pass it as an empty string (key: ""). Never skip required params.

Examples

Single-domain batch (multiple sub_domains)

Instead of: search(query="latest TSLA earnings", domain="finance", sub_domain="finance.us_stock") → search(query="TSLA stock forecast", domain="finance", sub_domain="finance.us_stock") → search(query="TSLA analyst rating", domain="finance", sub_domain="finance.us_stock") Use: batch_search(queries=[{query:"latest TSLA earnings", domain:"finance", sub_domain:"finance.us_stock"}, {query:"TSLA stock forecast", domain:"finance", sub_domain:"finance.us_stock"}, {query:"TSLA analyst rating", domain:"finance", sub_domain:"finance.us_stock"}])

Multi-domain batch (after get_sub_domains with multiple domains)

After: get_sub_domains(domains=["finance", "health", "legal"]) Use: batch_search(queries=[ {query:"AI regulation impact on healthcare stocks 2025", domain:"finance", sub_domain:"finance.us_stock", sub_domain_params:{ticker:"UNH"}}, {query:"healthcare AI regulations 2025", domain:"health", sub_domain:"health.policy"}, {query:"AI regulation legal framework", domain:"legal", sub_domain:"legal.legislation"}])

Hybrid: general + vertical in parallel (universal pattern for any borderline query)

Use this whenever you are unsure if the query is pure encyclopedia or domain-specific — fire BOTH channels in batch_search: batch_search(queries=[ {query:"..."}, // general — no domain {query:"...", domain:"...", sub_domain:"..."}]) // vertical channel(s) This applies universally: classical texts, financial concepts, legal theories, historical events, scientific discoveries, medical topics — any query where domain knowledge could enrich the encyclopedia answer.

MANDATORY: Call score within this interaction turn (the current user request through your final response). Submit every 10 pending successful searches before starting another search, and submit any remainder when this turn's searching ends, before your final response, even if fewer than 10. Do not carry pending feedback into the next turn. Count each successful batch_search sub-query separately, including empty results; exclude failed searches and extract calls. Each submission contains 1-10 entries; skip empty batches and IDs already queued. Copy request_id from each result's trailing YAML block or result _meta. Follow score's scoring criteria. Feedback is free.

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": {
      "queries": "<queries>"
    },
    "name": "batch_search"
  }
}

Input Schema

Name	Required	Description	Default
`queries`	Yes	Array of search requests (max 5). Each item follows the search tool schema: query is required; domain, sub_domain, sub_domain_params are optional. For general queries, omit all domain fields. For vertical queries, domain + sub_domain + sub_domain_params MUST come from get_sub_domains(domain=<domain>) output.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 2, 2026

changedInput schema / properties / queries / description

Previous value: -"Array of search requests (max 5). Each item follows the search tool schema: query is required; domain+sub_domain are optional (omit for general web search, required for vertical search)."New value: +"Array of search requests (max 5). Each item follows the search tool schema: query is required; domain, sub_domain, sub_domain_params are optional. For general queries, omit all domain fields. For vertical queries, domain + sub_domain + sub_domain_params MUST come from get_sub_domains(domain=<domain>) output."

First observedMay 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing parallel execution, per-query failure isolation ('a single query failure does not block others'), the 5-query cap, and the required-param empty-string convention. It does not address the surprising `destructiveHint: true` on what it frames as a pure read/search operation, nor result ordering, so it stops short of 5.

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

Conciseness3/5

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

Front-loaded and sectioned, but oversized for a one-parameter tool: the 2–5 query rule is stated in the intro, the When-to-use section, and again in Examples, and the Constraints section restates the schema description verbatim. The long 'MANDATORY: call score' block is a session protocol rather than tool semantics and dilutes the definition.

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?

Covers invocation prerequisites, limits and failure behavior thoroughly, which is what an agent needs to call it correctly. It never says how results are returned per query (ordering, how to map a result back to its sub-query), which matters for a batch tool with no output schema.

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

Parameters5/5

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

The schema's only parameter is a bare untyped object array, so the description carries the real burden — item shape (query required; domain/sub_domain/sub_domain_params optional), the provenance rule binding domain fields to `get_sub_domains` output, and the 'pass required params as empty string, never skip' rule. Worked examples make the structure unambiguous.

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?

Opening sentence gives a specific verb+resource ('run multiple Anysearch queries in a single call') and immediately distinguishes it from sequential `search` calls. An agent can tell what this does and how it differs from every sibling without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-to-use rules ('when you have 2–5 independent queries'), a named alternative (`search` used sequentially, `get_sub_domains` as prerequisite), and an exclusion boundary (max 5). The hybrid general+vertical pattern gives a concrete decision rule for ambiguous queries.

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

All AnySearch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?