Skip to main content
Glama
lennney

Agent Search MCP

free_search_advanced

Read-onlyIdempotent

Perform filtered multi-source searches with domain control and confidence scoring. Supports Chinese content and waterfall progressive search to reduce engine calls.

Instructions

Advanced search with filters and quality control.

Best for: Domain filtering, high-confidence only, Chinese content. Not recommended for: Simple queries — use free_search instead.

@readOnly true @idempotent true — runs waterfall progressive search across policy-allowed engines. Makes outbound HTTP requests to search engines and optionally to Jina Reader for content enrichment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results (1-20)
queryYesSearch query
enrichNoEnable content enrichment (extract full page for low-confidence results)
languageNoLanguage preferenceauto
waterfallNoEnable waterfall progressive search (saves engine calls)
enrich_maxNoMax results to enrich per search
time_rangeNoDeprecated compatibility field; returns UNSUPPORTED_FILTER because general-search recency is not enforced end to end
min_confidenceNoMinimum source-reliability confidence (0-1). Legacy values 2-3 are treated as min_source_count.
exclude_domainsNoExclude these domains
include_domainsNoOnly search these domains
min_source_countNoMinimum independent upstream provider families; current adapters expose at most 12
waterfall_min_resultsNoMinimum results per phase for waterfall confidence check
waterfall_min_confidenceNoMinimum average confidence to stop waterfall early

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaYes
queryYes
enginesYes
resultsYes
cache_hitNo
rate_limitsNo
security_noteYes
partialFailuresNo
detected_languageNo
Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds valuable context: 'runs waterfall progressive search across policy-allowed engines. Makes outbound HTTP requests to search engines and optionally to Jina Reader for content enrichment.' This explains the tool's external calls and algorithmic behavior beyond the annotations.

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 very concise: three sentences plus two lines. The structure clearly separates purpose, best-for, and behavioral notes. Every sentence adds value, with no redundancy.

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?

The tool has 13 parameters and an output schema. The description explains the high-level search mechanism (waterfall, enrichment, engine calls), which is sufficient for understanding. However, it could briefly mention the confidence waterfall logic to improve completeness, but it's still strong.

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 description coverage is 100%, so all parameters already have descriptions. The tool description adds general context about waterfall and enrichment but does not add specific parameter-level details beyond what the schema provides. Baseline 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 starts with 'Advanced search with filters and quality control,' which is a specific verb+resource combo. It explicitly distinguishes from sibling 'free_search' by stating 'Not recommended for: Simple queries — use free_search instead.' This clearly differentiates the tool's role.

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 provides explicit 'Best for' scenarios (domain filtering, high-confidence only, Chinese content) and a clear 'Not recommended for' with an alternative tool name. This helps agents decide when to invoke this tool versus its sibling.

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/lennney/agent-search-mcp'

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