Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

startpage_suggest

Generate up to 10 Startpage autocomplete suggestions for a query prefix, ranked in Startpage order, to aid search query discovery and autocomplete features.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query prefix
countNoSuggestions to return; defaults to 10, clamped to 1..10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/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 it does disclose real behavior: results come back in Startpage's own ranking order and never exceed 10 suggestions per prefix regardless of how many are requested. That server-side cap and ordering note are genuinely useful and not derivable from the schema alone. It stops short of 5 because safety/read-only status and any rate-limit or failure behavior are unstated.

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?

Three short sentences, front-loaded with what the tool does before the behavioral details. Every sentence earns its place and nothing is repeated from structured fields unnecessarily.

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 simple two-parameter suggest tool with no output schema, the description covers the essentials: what is returned, ordering, and the hard cap. It would be stronger if it briefly described the return shape (e.g. a list of suggestion strings), which is the only notable gap.

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 both parameters are already documented in the schema, and the baseline is 3. The description restates that input is a query prefix but adds no syntax, length limits, or encoding guidance beyond what the schema provides.

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 and resource: returns Startpage search-box autocomplete completions for a query prefix. An agent can tell it apart from the many other *_suggest siblings by the Startpage brand in the name and description. It does not explicitly contrast itself with alternatives such as google_suggest or duckduckgo_suggest, so it stops short of a 5.

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: an agent can infer this tool is for expanding a partial query into suggestions, and the 'query prefix' framing makes the trigger condition reasonably clear. However, there is no explicit when-to-use/when-not statement and no mention of which sibling suggest tool to prefer when the target engine is unspecified.

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