push_contempt_mcp

Overview Schema Source Related Servers Discussions Admin

prodotti_sotto_scorta

Identify published WooCommerce products that are out of stock or below a stock threshold, ordered by restocking urgency.

Instructions

Prodotti pubblicati esauriti o con scorte sotto soglia (solo quelli con gestione scorte attiva in WooCommerce - per gli altri conta solo lo stato esaurito/in attesa, non c'è un numero di scorte attendibile). Esauriti per primi, poi per scorte crescenti: utile per capire cosa rifornire con più urgenza.

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": "prodotti_sotto_scorta"
  }
}

Input Schema

Name	Required	Description	Default
`soglia`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses result ordering (out-of-stock first, then ascending stock) and an important data-quality caveat that products without active stock management only report status, not a reliable stock count. It does not mention pagination or result limits, which is a smaller gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the scope and caveat before the ordering and use-case rationale. No filler, though it could be tighter.

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?

An output schema exists, so return values need no explanation. The description covers scope, ordering, and the stock-management caveat; only the read-only nature and any result limits are left implicit.

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 0% and the single parameter only shows a default of 5, so the description must compensate. It does so by explaining that `soglia` is the stock threshold below which products are returned, which is more than the bare schema provides.

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 concrete verb-less but clear purpose: products that are sold out or have stock below `soglia`, with an explicit scope caveat about WooCommerce stock management. An agent can distinguish it from `lista_prodotti`, though no sibling is named directly.

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?

The closing clause 'utile per capire cosa rifornire con più urgenza' implies the use case (restocking prioritization), but there is no explicit when-to-use versus when-not guidance and no named alternative among the many product-listing siblings.

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