Skip to main content
Glama

anysearch_get_sub_domains

Discovers available sub-domains and structured parameters for any specified search domain. Required first step before performing vertical searches for finance, health, academic, and other specialized topics.

Instructions

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:

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

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.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that the tool is a discovery step (read-only), describes the return format, and gives critical instructions on parameter handling. Minor missing info on permissions or side effects, but overall transparent.

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

Conciseness4/5

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

Description is relatively long but well-structured with sections and bullet points. Front-loaded with purpose and importance. Could be slightly trimmed but every section adds necessary context.

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?

Given 2 parameters, no output schema, and complexity (multiple domains, structured params), the description is very complete. It explains what is returned (markdown table), how to use results, and integrates with sibling tools like batch_search and search.

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% with clear enum descriptions. Description adds significant value: explains the mutual exclusivity of domain vs domains, strongly recommends using 'domains', shows example queries, and clarifies how to interpret the params column in results.

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 it is a domain discovery tool for vertical search, prerequisite for searches that use a domain. It distinguishes itself from sibling tools like anysearch_search by being step 1 and returning sub_domains and params.

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?

Provides explicit when-to-call guidance with a list of domains, recommends using the plural 'domains' parameter with examples, and explains how to use results (sub_domain as primary key, pass params via sub_domain_params, use batch_search for multiple sub_domains).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Microbiosis/mini-agent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server