Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

psastore_product_recommendations

Get related or complementary product recommendations for a PSA Team Store item by handle, with optional limits, to support cross-sell and product discovery.

Instructions

List PSA Store product recommendations. Returns recommended products for one PSA Team Store (https://store.psacard.com) product handle. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum products, defaults to 10 and supports up to 20
handleYesProduct handle
intentNoRecommendation intent. Allowed values: related, complementary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses read-like behavior ('List', 'Returns') and notes the storefront URL is fixed server-side, but omits auth, rate limits, pagination, and side-effect details.

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 purpose and followed by return scope and a server-side constraint. No filler or redundant repetition.

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

Completeness3/5

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

For a simple recommendation list with no output schema or annotations, the description covers purpose and basic return scope. It stops short of output shape, auth, or pagination, leaving some 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 description coverage is 100%, so the parameters are largely self-documenting. The description reinforces that 'handle' identifies one product but adds no meaning for 'limit' or 'intent' beyond what the schema already states.

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 ('List') and resource ('PSA Store product recommendations'), and scopes it to a single product handle. It clearly distinguishes recommendations from product listings/detail, though it does not name sibling tools.

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?

Implied usage: call when you have a product handle and want recommended products. No explicit when-not-to-use, alternative tools, or prerequisites are provided.

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