Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ohpolly_collections

Fetch paginated Oh Polly collections as normalized JSON, with page and limit controls to browse the storefront catalog.

Instructions

List Oh Polly collections. Returns normalized collections from Oh Polly (https://www.ohpolly.com). The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty collections array.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum collections, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses meaningful details: normalized output, a server-side fixed storefront URL, and the 200-with-empty-array behavior for valid empty result pages. These are useful beyond the schema.

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-load the main action and each sentence adds value: what the tool lists, where data comes from, and an important edge-case behavior. No filler or redundancy.

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 list tool with two optional pagination parameters, the description covers the source, normalization, and empty-page behavior. It lacks explicit return-field details, but there is no output schema and the tool's purpose is straightforward enough that this is a minor gap.

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 page and limit are already self-documented. The description adds only marginal context about pages and empty results, not new parameter semantics, so the baseline of 3 is appropriate.

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?

The description uses a specific verb ('List') and resource ('Oh Polly collections'), names the source URL, and states it returns normalized collections. This clearly distinguishes it from siblings like ohpolly_collection_products and ohpolly_product.

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?

The intended use is implied: use this tool when you need the list of Oh Polly collections. However, there is no explicit guidance about when to prefer this over related siblings such as ohpolly_collection_products or ohpolly_products.

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