Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sevennow_suggest

Get 7NOW search-term completions for a partial query of at least three characters, with vertical-specific suggestions for convenience, restaurant, or global indexes.

Instructions

Get 7NOW search-term suggestions. Returns search-term completions for a partial query, e.g. "chi" -> "chips ahoy", "chips", "chicken". No store is required. q must be at least 3 characters -- shorter values return a typed invalid-param error, matching upstream's own enforced minimum. vertical selects which search index to complete against, and the indexes are materially different rather than variations on one list: for "chi", convenience answers "chips ahoy, chips, chicken wings" while restaurant answers "chipotle, chinese food, chili". global is a sparse cross-vertical index -- many prefixes legitimately return no suggestions there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesPartial search term, at least 3 characters.
verticalNoWhich search index to complete against. One of: convenience, restaurant, global. Defaults to convenience.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / vertical / enum
      Added value: +[
+  "convenience",
+  "restaurant",
+  "global"
+]
  2. Addedv1.16.2

TDQS

A4.6/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden, and it does so well. It discloses upstream's enforced 3-character minimum and its typed invalid-param error, states that no store is required, and documents that verticals are not interchangeable and that global is a sparse index.

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?

The description is front-loaded with the core purpose and example, and every substantive sentence earns its place. Minor redundancy between 'Get 7NOW search-term suggestions' and 'Returns search-term completions for a partial query' keeps it from a perfect conciseness score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema, the description covers the return behavior, the minimum-input constraint, vertical semantics, the no-store precondition, and the sparse-global caveat. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful value beyond the schema by explaining the failure mode for short q values and by giving worked examples of how convenience, restaurant, and global return different suggestions for the same prefix.

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?

States a specific verb and resource: it returns search-term completions for a partial query, with a concrete example ("chi" -> "chips ahoy", "chips", "chicken"). The description makes it unmistakable that this is an autocomplete/suggest tool rather than a full search or catalog tool.

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?

Provides clear operational context: no store is required, q must be at least 3 characters, and the vertical parameter selects materially different search indexes, including a warning that global may legitimately return nothing. It does not explicitly name an alternative sibling such as sevennow_search, so it stops short of a 5.

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