Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sparkfun_product

Fetch SparkFun product details by SKU, including stock, price, images, categories, description, and recommendations. Use it to resolve product lookups or detect unknown SKUs via 404.

Instructions

Get a SparkFun product. Returns one SparkFun product by sku, for example DEV-18158: name, URL, stock status, current minimum price and currency, main image and media gallery, categories, and a cleaned short description. recommendations lists related, upsell or crosssell products when available. An unknown SKU returns 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuYesSparkFun product SKU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4/5.0
Behavior4/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 does so well by enumerating the returned fields (name, URL, stock status, min price/currency, images, categories, short description) and the `recommendations` field, plus the 404 error behavior. It omits auth or rate-limit details, keeping it from a 5.

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 sentences, all front-loaded and information-dense: purpose first, then return contents, then error behavior. No filler sentences.

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 no output schema and no annotations, the description compensates fully by describing the return fields and the unknown-SKU behavior. An agent has everything needed to call it and interpret the result.

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 the baseline is 3, but the description adds value by giving a concrete SKU format example ('DEV-18158') that clarifies how the parameter is shaped.

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?

The description states a specific verb+resource ('Get a SparkFun product') and scopes it to retrieval by `sku`. It is clearly distinct from search/category siblings in effect, though it never names those alternatives explicitly, so it stops short of a 5.

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 required `sku` and the worked example ('DEV-18158'), and the 404 case tells the agent what happens on an unknown key. However, there is no explicit guidance on when to use this versus sparkfun_search or sparkfun_categories, so the routing is left to inference.

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