Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brave_suggest

Generate Brave search query suggestions from a prefix to speed up query building and autocomplete. Add locale and entity metadata for richer results.

Instructions

Suggest Brave search queries. Returns Brave autosuggest query completions for a query prefix. Locale defaults to country=us and lang=en-us. Suggestions are fetched from public Brave Search suggest JSON and trimmed to the requested count. rich=true adds entity metadata (name, description, category, image) where Brave resolves a suggestion to a known entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query prefix
langNoBrave UI language; defaults to en-us
richNoAdd entity name, description, category, and image to suggestions Brave resolves to a known entity; defaults to false
countNoSuggestions to return; defaults to 10, clamped to 1..12
countryNoBrave result country; defaults to us

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.9
    • addedInput schema / properties / rich
      Added value: +{
+  "description": "Add entity name, description, category, and image to suggestions Brave resolves to a known entity; defaults to false",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / country / enum
      Added value: +[
+  "all",
+  "ar",
+  "at",
+  "au",
+  "be",
+  "br",
+  "ca",
+  "ch",
+  "cl",
+  "cn",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hk",
+  "id",
+  "in",
+  "it",
+  "jp",
+  "kr",
+  "mx",
+  "my",
+  "nl",
+  "no",
+  "nz",
+  "ph",
+  "pl",
+  "pt",
+  "ru",
+  "sa",
+  "se",
+  "sg",
+  "tr",
+  "tw",
+  "us",
+  "za"
+]
    • addedInput schema / properties / lang / enum
      Added value: +[
+  "de-de",
+  "en-ca",
+  "en-gb",
+  "en-in",
+  "en-us",
+  "fi-fi",
+  "fr-ca",
+  "fr-fr",
+  "ja-jp",
+  "pt-br",
+  "sq-al",
+  "sw-ke",
+  "zh-tw"
+]
  3. Addedv1.6.0
  4. Removedv1.6.0
  5. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does reasonably well: it discloses the default locale (country=us, lang=en-us), the data source (public Brave Search suggest JSON), count trimming, and what rich=true adds. It omits error/rate-limit behavior or whether suggestions can be empty.

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?

Four sentences, all front-loaded with the core purpose first, then defaults, source, and the rich option. Slightly redundant with schema-documented defaults (country/lang), but no filler.

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 5-param tool with no output schema and no annotations, the description covers purpose, defaults, data source, and the optional rich metadata return content. It is complete enough to call correctly, though return value structure beyond content is left implicit.

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 five parameters are already documented, including defaults and enums. The description restates locale defaults and the rich flag but adds little syntax or semantics beyond the schema, so the baseline 3 applies.

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+resource ('Suggest Brave search queries') and clarifies the return is autosuggest query completions for a prefix. This distinguishes it from siblings like brave_search, brave_news, and brave_images, which return full results rather than completions.

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 only implied: 'for a query prefix' hints at autocomplete/typeahead use, but there is no explicit statement of when to use this over brave_search or other Brave tools, and no exclusions or prerequisites. The agent must infer the routing.

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