Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

psastore_search_suggest

Retrieve PSA Team Store predictive search suggestions for products, collections, and queries. Input a search term to get up to 20 results per type.

Instructions

Get PSA Store search suggestions. Returns products, collections, and query suggestions from the PSA Team Store's (https://store.psacard.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the storefront URL is fixed server-side (no URL parameter needed) and what categories of suggestions come back, but says nothing about authentication, rate limits, pagination, or how suggestion ranking works.

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 tight sentences with the core purpose front-loaded and the server-side URL constraint appended as a useful, non-redundant note. No filler or repeated schema content.

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 low-complexity suggestion tool with full param coverage and no output schema, the description adequately covers what it does and what it returns (products, collections, query suggestions). Authentication and pagination behavior are the only meaningful gaps.

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 coverage is 100%, so the schema already documents q, limit, and types in full. The description echoes the type categories (products, collections, query) that map to the 'types' parameter, adding marginal reinforcement but no syntax or default details beyond the schema.

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 ('Get') and resource ('PSA Store search suggestions') and further clarifies the return payload as products, collections, and query suggestions from a predictive search. An agent can tell it apart from the psastore_products/psastore_collections siblings as a suggestion/typeahead endpoint, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The 'predictive search' framing implies a typeahead/autocomplete use case, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many psastore_* and *_search_suggest siblings. The agent must infer that this is for suggestion lookup rather than full product search.

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