Skip to main content
Glama

AnySearch

by com.anysearch.api
OverviewDiscussionsAdmin

get_sub_domains

Read-onlyDestructive

This is Anysearch's domain discovery tool. IMPORTANT: Step 1 of vertical search. REQUIRED before any search that uses a domain. Returns valid sub_domains and sub_domain_params for the specified domain(s).

Call this when the query targets a specialized vertical or needs structured parameters: stock prices, financial data, academic papers, legal cases, medical/drug info, flight status, weather, exchange rates, geographic POIs, code repositories, or any domain where a structured identifier (ticker, DOI, CVE, IATA, coordinates) is involved.

When to call ā€” pick the domain(s) that match what the user is asking about:

academic agriculture business code energy environment film finance gaming health ip legal resource security social_media travel

Input ā€” choose from the list above and pass via the domain or domains parameter:

  • domain: single domain string (use only when 100% certain the query is single-domain)

  • domains: batch query for up to 5 domains in one call (takes priority over domain)

šŸ† ALWAYS prefer the domains (plural, array) parameter. Pass ALL potentially relevant domains at once ā€” even for seemingly single-domain queries, consider related domains:

  • Query about "cryptocurrency regulations" ā†’ domains=["finance", "legal", "security"]

  • Query about "best gaming laptops" ā†’ domains=["gaming", "tech", "ecommerce"]

  • Query about "climate change impact on agriculture" ā†’ domains=["environment", "energy", "academic"]

Returns

Markdown table filtered to the specified domains: sub_domain | description | params

CRITICAL: How to use results

  • sub_domain is the PRIMARY routing key ā€” always pass it to search

  • params column shows available structured parameters ā€” pass them via sub_domain_params in search, NEVER embed in query

  • If multiple sub_domains returned (especially from multiple domains), use batch_search ā€” one query per sub_domain ā€” instead of multiple sequential search calls

  • Params marked (required) in the output MUST be passed when using that sub_domain in search. If a required param is not applicable to your query, pass it as an empty string (key: "") ā€” do not skip it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoFilter by a single domain. Mutually exclusive with domains array.
domainsNoBatch query for multiple domains in a single call. Takes priority over domain. Each item must be a valid domain value. Max 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "general",
-  "resource",
-  "social_media",
-  "finance",
-  "academic",
-  "legal",
-  "health",
-  "business",
-  "security",
-  "ip",
-  "code",
-  "energy",
-  "environment",
-  "agriculture",
-  "travel",
-  "film",
-  "gaming"
-]New value: +[
+  "academic",
+  "agriculture",
+  "business",
+  "code",
+  "energy",
+  "environment",
+  "film",
+  "finance",
+  "gaming",
+  "general",
+  "health",
+  "ip",
+  "legal",
+  "resource",
+  "security",
+  "social_media",
+  "travel"
+]
    • changedInput schema / properties / domains / items / enum
      Previous value: -[
-  "general",
-  "resource",
-  "social_media",
-  "finance",
-  "academic",
-  "legal",
-  "health",
-  "business",
-  "security",
-  "ip",
-  "code",
-  "energy",
-  "environment",
-  "agriculture",
-  "travel",
-  "film",
-  "gaming"
-]New value: +[
+  "academic",
+  "agriculture",
+  "business",
+  "code",
+  "energy",
+  "environment",
+  "film",
+  "finance",
+  "gaming",
+  "general",
+  "health",
+  "ip",
+  "legal",
+  "resource",
+  "security",
+  "social_media",
+  "travel"
+]
  2. Added

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), and the description adds context about output format (Markdown table) and the critical role of sub_domain as a routing key. It does not clarify the inconsistent destructiveHint=true annotation, but it also does not contradict it; the description's read-only framing aligns more with readOnlyHint. Lacking explicit mention of side effects or edge cases, but the lower bar is met.

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 long but every section earns its place: purpose, when-to-call, input guidance, return format, and critical downstream usage. It is front-loaded with the most important constraint and uses clear headings and bullet lists that make scanning easy. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully compensates by describing the Markdown table columns and explaining how to handle required params (pass as empty string) and when to switch to batch_search. It covers both parameters in depth and provides a complete operational picture for an agent.

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?

Schema coverage is 100%, yet the description goes far beyond field names. It explains when to use 'domain' vs 'domains' ('use only when 100% certain', 'takes priority over domain'), enforces a preference for the plural form, and gives concrete examples of combined domain selection. This is substantial added meaning.

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 states a specific verb and resource ('domain discovery tool', 'Returns valid sub_domains and sub_domain_params') and explicitly positions it as 'Step 1 of vertical search' required before any search. It lists concrete use cases (stock prices, academic papers, legal cases, etc.) that distinguish it from the sibling search and batch_search tools.

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?

The description gives explicit when-to-call criteria with examples, a full domain list, and clear routing to batch_search when multiple sub_domains are returned. It even prescribes parameter choice ('ALWAYS prefer the domains (plural, array) parameter') and provides example mappings from query types to domains. This is model-level guidance.

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

All AnySearch toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources