Crawlora MCP

sparkfun_category

Read-only

Fetch paginated SparkFun product records for category url_key, with dynamic facet filters from the response; pass each filter as attribute:value. Use sparkfun_categories to discover categories or sparkfun_search for free-text search.

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": {
      "url_key": "<url_key>"
    },
    "name": "sparkfun_category"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based result page (1-100)
`filter`	No	Repeatable dynamic facet in attribute:value form
`url_key`	Yes	SparkFun category URL key
`per_page`	No	Products per page (1-24)

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.

Changed4 schema fields changedOct 7, 2026
- addedInput schema / properties / filter / description
```
Added value: +"Repeatable dynamic facet in attribute:value form"
```
- addedInput schema / properties / page / description
```
Added value: +"One-based result page (1-100)"
```
- addedInput schema / properties / per_page / description
```
Added value: +"Products per page (1-24)"
```
- addedInput schema / properties / url_key / description
```
Added value: +"SparkFun category URL key"
```
First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds that results are paginated and that valid facet filters are dynamic and derived from the response rather than a fixed list. That facet-discovery behavior is genuinely useful and not in the structured fields, though auth/rate-limit details are absent.

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 tight sentences: capability and facet mechanism first, sibling routing second. No filler and nothing buried.

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?

With an output schema present, annotations covering the safety profile, and complete parameter docs, the description supplies everything else an agent needs: pagination awareness, dynamic facet handling, and correct sibling routing.

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 page, per_page, filter, and url_key are already documented. The description's 'attribute:value' phrasing largely repeats the schema's 'Repeatable dynamic facet in attribute:value form', adding only the note that facets come from the response.

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 and resource ('Fetch paginated SparkFun product records for category url_key') and scopes it with pagination and facet filtering. It is immediately distinguishable from sparkfun_categories (category discovery) and sparkfun_search (free-text).

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

Usage Guidelines5/5

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

Explicitly routes the agent: use sparkfun_categories to discover categories, sparkfun_search for free-text, and this tool when you already have a url_key and/or facet filters. Both alternatives and the selecting condition are named.

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?