Crawlora MCP

kroger_suggest

Read-only

Kroger's own search-box suggestions for a (possibly empty) query, sourced from Kroger's public suggestions API. An empty query returns default "trending" shopping shortcuts instead of an error. location_id scopes results to one Kroger store and defaults to a confirmed-working store id when omitted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kroger_suggest"
  }
}

Input Schema

Name	Required	Description	Default
`Query`	No	Partial search text; omit for trending default suggestions
`LocationID`	No	Kroger store/location id

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / LocationID / description
```
Added value: +"Kroger store/location id"
```
- addedInput schema / properties / Query / description
```
Added value: +"Partial search text; omit for trending default suggestions"
```
First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only/open-world safety, but the description adds real behavioral context: it is sourced from Kroger's public suggestions API, empty queries return trending defaults rather than erroring, and location_id defaults to a confirmed-working store. It stops short of describing result count or shape.

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 tight sentences, front-loaded with the core purpose and followed by the key edge case and default. Only the API-sourcing clause is mildly filler, but it justifies the open-world hint.

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 an autocomplete tool with an output schema, annotations, and full schema coverage, the description covers the one thing an agent would otherwise get wrong: empty input returns trending suggestions, not an error, and location scoping defaults sensibly.

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 schema already documents both params (baseline 3). The description adds meaningful default/edge-case semantics — empty Query yields trending shortcuts, omitted LocationID falls back to a working store id — going beyond the schema's plain field descriptions.

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+resource: Kroger's own search-box suggestions/autocomplete for a query. An agent can distinguish this from kroger_search (full search) and kroger_product without opening a schema.

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?

Explains the empty-query path (returns trending shortcuts instead of an error) and the location scoping, which implies usage, but never explicitly says when to reach for this over kroger_search or other Kroger siblings.

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

All Crawlora MCP tools Inspect

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

Need Help?