Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

duckduckgo_suggest

Get DuckDuckGo search-box autocomplete completions for a query prefix, ranked in DuckDuckGo order, to build query suggestions. Returns up to 8 per prefix.

Instructions

Suggest DuckDuckGo search queries. Returns DuckDuckGo search-box autocomplete completions for a query prefix, in DuckDuckGo's own ranking order. DuckDuckGo never returns more than 8 suggestions per prefix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query prefix
countNoSuggestions to return; defaults to 8, clamped to 1..8
regionNoDuckDuckGo region code such as us-en, uk-en, de-de, or wt-wt (worldwide, the default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral value: results come in DuckDuckGo's own ranking order and are capped at 8 per prefix. It does not mention auth, rate limits, or empty-result behavior, but for a public read-only autocomplete endpoint the disclosed ordering and cap are the salient traits.

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?

Three short sentences, front-loaded with the purpose and then the return behavior. Slightly redundant in restating 'suggest DuckDuckGo search queries' as 'DuckDuckGo search-box autocomplete completions,' but every sentence still carries information.

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?

For a 3-parameter, read-only autocomplete tool with no annotations and no output schema, the description covers purpose, input interpretation, result ordering, and the 8-item cap. An agent has enough to call it correctly; only edge behavior (empty prefixes, region defaults) is left to the schema.

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 coverage is 100%, so q, count, and region are already documented in the schema. The description's 'query prefix' phrasing reinforces the q semantics but adds nothing about count or region beyond what the schema states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (suggest DuckDuckGo search queries) and clarifies it returns autocomplete completions for a query prefix, which distinguishes it from duckduckgo_search. It does not explicitly name the sibling it is not, but the autocomplete framing is clear enough for an agent to differentiate.

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

Usage Guidelines3/5

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

Usage is implied by 'autocomplete completions for a query prefix' — an agent can infer this is for prefix/completion lookup rather than full search. However, it never states when to prefer this over duckduckgo_search or over other suggest tools like google_suggest or bing_suggest, and there are no exclusions.

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

Deploy Server

Other Tools