Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wayfair_category

Read-only

Browse a Wayfair category page's product grid, with real page-based pagination: normalized products with name, brand, pricing, and image. category accepts a bare Wayfair category id, a "c"-prefixed id, a category slug, or a full category URL -- only the trailing category id is used.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "wayfair_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1-based, defaults to 1
categoryYesWayfair category id, slug, or URL

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Wayfair category id, slug, or URL"
    • addedInput schema / properties / page / description
      Added value: +"Result page, 1-based, defaults to 1"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), so the bar is lower; the description still adds real context by disclosing that pagination is genuine page-based rather than offset/scroll, and enumerates the returned normalized fields. No contradictions with annotations.

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?

Two sentences, zero waste, with the core action front-loaded and the identifier-format caveat placed second. Every clause earns its place.

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?

With an output schema present, the description needn't detail return values, yet it usefully summarizes normalized fields and pagination behavior. The main gap is the absence of routing guidance against its two Wayfair siblings.

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 baseline is 3, but the description goes beyond the schema's terse 'Wayfair category id, slug, or URL' by spelling out that a bare id, 'c'-prefixed id, slug, or full URL are all accepted and that only the trailing category id is used. That is format guidance the schema does not carry.

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 and resource: 'Browse a Wayfair category page's product grid,' and adds what the grid contains (normalized products with name, brand, pricing, image). It's distinct from wayfair_product and wayfair_categories, though it never names those siblings to sharpen the contrast.

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?

Usage is implied by the resource ('category page's product grid') and the pagination note, but there is no explicit when-to-use versus wayfair_categories (to discover ids) or wayfair_product (a single item). An agent must infer the routing.

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

All Crawlora MCP toolsInspect
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