Skip to main content
Glama
Sign In
CommerceWeave MCP

CommerceWeave MCP

by mysterekkk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find products running low

commerce_low_stock
Read-onlyIdempotent

List sellable product variants at or below a stock threshold across connected stores, lowest first, while reporting skipped unmanaged quantities and incomplete or failed connections.

Instructions

Lists sellable items (variants individually) with stock <= threshold on each connection, lowest first. Items whose platform does not manage a quantity are skipped and counted, never treated as zero. Reports which connections were incomplete or failed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "commerce_low_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNo
connectionIdsNoConnection ids to include (see commerce_list_connections). Omit for all connections.
maxItemsPerConnectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world. The description adds genuinely new behavior: items whose platform does not track quantity are skipped and counted rather than treated as zero, and incomplete or failed connections are reported - important for interpreting results as partial.

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 tight sentences, front-loaded with the core behavior, then edge-case handling, then reporting caveats. 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 3-parameter read tool with no output schema, the description covers return ordering, granularity, exclusion handling and partial-failure reporting. The main gap is what happens when maxItemsPerConnection is hit, which an agent would need before trusting completeness of results.

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 33%: only connectionIds is documented in the schema, and the description reinforces it ('on each connection') and clarifies threshold semantics ('stock <= threshold'). maxItemsPerConnection is never mentioned, so truncation behavior at that cap is undocumented in both schema and description.

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 plus scope: 'Lists sellable items (variants individually) with stock <= threshold on each connection, lowest first.' That granularity (variant-level, ordered ascending, per-connection) distinguishes it from a plain product listing or an inventory summary, though it never names a sibling tool outright.

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 title and phrase 'with stock <= threshold,' so an agent can infer this is the low-stock query. However, there is no explicit when-to-use versus when-not guidance and no pointer to alternatives such as the discrepancy or inventory report tools, leaving routing 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