Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

startpage_suggest

Read-only

Returns Startpage search-box autocomplete completions for a query prefix in Startpage's own ranking order. Use for keyword ideas from a privacy-focused engine; returns at most 10 suggestions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "startpage_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query prefix to autocomplete. Required, e.g. openai.
countNoSuggestions to return, default 10, clamped to 1..10 (Startpage never returns more than 10).

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations (readOnlyHint=true, openWorldHint=true) already establish this is a safe, open-web read. The description adds the output ordering ('Startpage's own ranking order') and a 10-suggestion cap, but the cap is already stated in the schema's count parameter, leaving only ranking order as net-new behavioral context.

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?

Two tightly written sentences with the core purpose front-loaded. The trailing 'returns at most 10 suggestions' clause partially duplicates the count parameter's schema description, a minor redundancy that keeps it from a full 5.

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 autocomplete tool with an output schema and full schema coverage, the definition covers purpose, usage context, and result limit. An output schema exists so return values need no explanation; only sibling differentiation is missing.

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 'q' (prefix) and 'count' (default 10, clamped 1..10) are fully documented in the schema. The description adds no syntactic or format detail beyond that, which is the correct baseline when the schema does the heavy lifting.

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. The 'Startpage's own ranking order' and 'privacy-focused engine' phrasing gives some implicit differentiation from other search suggestions, but it never names a sibling (e.g., google_suggest) to route against, so it falls 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 Guidelines4/5

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

Explicitly says to use it 'for keyword ideas from a privacy-focused engine,' which gives clear context for when the tool is appropriate. However, no exclusions or alternative-tool routing are provided, so the agent must infer that generic autocomplete for non-Startpage results belongs to a sibling suggest tool.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources