Skip to main content
Glama
Sign In
CommerceWeave MCP

CommerceWeave MCP

by mysterekkk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inventory overview per store

commerce_inventory_report
Read-onlyIdempotent

Summarizes per-connection inventory: sellable items, total units, and out-of-stock, low-stock, and unmanaged counts, so you can spot stock gaps across platforms without summing units.

Instructions

Per-connection inventory summary: number of sellable items, total units, out-of-stock, low-stock and unmanaged counts. Units are not summed across platforms because the same stock may be published in several places.

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_inventory_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
lowThresholdNo
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

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a genuinely important disclosure beyond them: units are deliberately not summed across platforms because stock may be duplicated, which prevents an agent from misinterpreting the totals. It stops short of disclosing truncation or pagination behavior.

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, both earning their place: the first front-loads what the report contains, the second carries the non-obvious aggregation caveat. No filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the necessary work of enumerating the returned counts, and annotations cover safety. However, it omits the semantics of lowThreshold and the truncation implied by maxItemsPerConnection, which matter for a capped, multi-connection report.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% — only connectionIds is documented in the schema. The description says nothing about lowThreshold (what makes an item 'low') or maxItemsPerConnection, which implies per-connection result truncation that an agent must know about. With a low coverage score the description needed to compensate and does not.

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 names a specific resource (inventory summary, per connection) and enumerates the metrics returned: sellable items, total units, out-of-stock, low-stock, unmanaged counts. That lets an agent distinguish it from a single-metric sibling like commerce_low_stock, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says whether to reach for this instead of commerce_low_stock or commerce_find_stock_discrepancies, and no prerequisites or scope conditions are given. The 'per-connection' framing implies an overview/reporting use case, but the agent must infer it.

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