Skip to main content
Glama
Octen-Team

octen-mcp

Official
by Octen-Team

broad_search

Expands a user's full question into multiple related sub-queries and searches them concurrently to provide broad multi-angle results for comparisons, surveys, and deep research.

Instructions

Broad multi-angle web search with Octen. Best for questions that span several subtopics where a single search only reaches a few: comparisons across many sources (pricing, products, vendors), surveys and deeper research, and any multi-angle question. Pass the user's full question as query AS-IS — Octen expands it into related sub-queries and searches them concurrently, returning results grouped per sub-query (not deduplicated). Do NOT pre-split the question or call this repeatedly; raise max_queries for broader coverage instead. For a single focused lookup, use search. Per-sub-query options (count, topic, language filter, domain / text filters, time window, highlight / full_content, media) are the same as search and apply to every sub-query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results to return (1-100). Default 5.
queryYesSearch query. Max 500 chars.
topicNoSearch category: `general` for broad web search, `news` for news-focused results. Default general.general
formatNoFormat of returned content. Default text.text
timeoutNoRequest timeout in seconds (1-60).
end_timeNoUpper bound for the time window, ISO 8601.
languageNoLanguages to filter results by, as ISO 639-1 codes. Empty = no filter.
highlightNoReturn a ranked highlighted snippet per result. Omit to use the server default.
safesearchNoAdult-content filter. Default strict.strict
start_timeNoLower bound for the time window, ISO 8601 (e.g. '2025-01-01T00:00:00Z').
time_basisNoWhich timestamp the time window filters against: page `published` date, last `crawled` date, or `auto`. Default auto.auto
time_rangeNoRelative time window (e.g. `week`, `month`). Mutually exclusive with `start_time`/`end_time` — if both are given, the absolute range wins.
max_queriesNoUpper bound on the number of sub-queries generated (1-30). Default 5 — raise toward 30 for surveys / deeper research, lower for a tighter search.
exclude_textNoDrop results whose content contains any of these strings. Max 5, each ≤30 chars.
full_contentNoReturn the cleaned full page body per result. Heavier than `highlight` — use only when the snippet isn't enough. Omit to use the server default (off).
include_textNoOnly return results whose content contains all of these strings. Max 5, each ≤30 chars.
include_imagesNoReturn image URLs (and a cover image) found on each result page.
include_videosNoReturn video URLs found on each result page.
exclude_domainsNoDrop results from these domains. Max 150, each ≤30 chars.
include_domainsNoOnly return results from these domains (e.g. 'arxiv.org'). Max 1000, each ≤30 chars.
Behavior5/5

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

No annotations exist, so the description fully handles behavioral disclosure. It explains that Octen expands queries into sub-queries, searches concurrently, returns results grouped per sub-query (not deduplicated), and that options apply uniformly. This gives the agent a clear mental model of the tool's operation.

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?

The description is moderately long but well-structured: purpose and key differentiator upfront, then use cases, then explicit instructions, then sibling contrast, then parameter behavior. Every sentence adds value, though some could be tightened.

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?

Despite 20 parameters, no output schema, and no annotations, the description covers all essential aspects: tool behavior, use cases, parameter guidance, and relationship with siblings. It is sufficiently complete for an agent to use the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds critical context: `query` must be passed AS-IS, `max_queries` controls sub-query generation, and all per-sub-query options apply equally. It also explains how parameters relate to the sibling tool `search`. This goes beyond the schema's basic descriptions.

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 specifies the tool as a 'Broad multi-angle web search' and lists concrete use cases (comparisons, surveys, deeper research) that distinguish it from a standard single-query search. It explicitly contrasts with the sibling tool `search`, ensuring the agent can differentiate.

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 guidance: when to use (multi-angle questions), when not to (use `search` for focused lookups), and how to adjust (`max_queries`). Also tells the agent not to pre-split the query or call repeatedly, which is critical for correct usage.

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/Octen-Team/octen-mcp'

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