Skip to main content
Glama

Push: Get Matched Product Logistics

get_push_shipping_recommendation
Read-onlyIdempotent

[Import List Product] [What it does] Reads publish-time logistics candidates for each exact Import List product and target-store pair. Product Core computes these candidates from both the product's logistics conditions and the target store's current logistics settings. Results apply only to their exact target and are not a general store shipping-method list, the supplier product's complete shipping catalog, or a supplier freight quote. [When to use] Use only when actively preparing an exact publish_products_to_stores call, once for every product-store target in that request. Do not call it for standalone or exploratory shipping queries. [When not to use] Do not use it to browse store or order logistics, publish or edit products, or estimate freight, landed cost, prices, or pricing formulas. For supplier-cost workflows, including requests to build pricing formulas, use list_supplier_product_shipping_methods_and_cost. [How to use]

  • import_list_ids and dsers_store_ids expand into a unique Cartesian product capped at 100 targets; copy IDs exactly from list_pre_publish_products and the store-discovery Tool.

  • If any requested target is missing, malformed, or hits an upstream error, the entire call fails instead of returning partial results.

  • Handle each result independently by its exact import_item_id and dsers_store_id. If logistics is non-empty, present only that target's candidates and ask whether the user wants to specify one. Selecting a candidate is optional; never choose for the user unless they already specified the exact service_id for that target.

  • If the user chooses a candidate, copy its exact service_id only to the matching publish_products_to_stores items[].stores[].shipping_method_id with the same import_item_id and dsers_store_id. Do not reuse a selection for another product-store target or derive it from company_name or another source.

  • If the user declines, does not choose one, or asks to use the default logistics, omit only that target's shipping_method_id. An empty logistics array is a successful and complete result for that pair; it does not mean the supplier product itself has no shipping methods or freight quote. Do not search the web, call another Tool or API to replace the result, infer a carrier, or manufacture a shipping method. Continue publishing that target with its default logistics.

  • amount belongs only to that publish candidate and is not a general supplier freight quote. It is a decimal string in major currency units, not a float. [Side effects] None; read-only and changes no product or store logistics settings. [Confirmation] Not required. [Follow-up] Return to the current publish_products_to_stores workflow; never reuse these results for another target or workflow.

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": {
      "import_list_ids": "<import_list_ids>",
      "dsers_store_ids": "<dsers_store_ids>"
    },
    "name": "get_push_shipping_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
dsers_store_idsYesOne or more dsers_store_id values returned by list_stores. Combined with every import_list_ids value; the unique matrix may contain at most 100 targets. Paste JSON example: ["1999323491106619392"].
import_list_idsYesOne or more import_item_id values returned by list_pre_publish_products or get_pre_publish_product. Combined with every store_ids value; the unique matrix may contain at most 100 targets. Paste JSON example: ["2085934367682592768"].

Output Schema

NameRequiredDescriptionDefault
itemsYesMatched publish-logistics candidates for every requested import-item/store target, in request matrix order
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Although annotations already declare readOnlyHint and idempotent, the description adds substantive behavior the annotations cannot express: all-or-nothing failure when any target is missing or malformed, a 100-target unique-matrix cap, empty logistics arrays being a valid complete result, and the requirement not to substitute web searches or other tools. It also specifies that amount is a decimal string in major units rather than a float.

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?

Bracketed section headers keep a long definition scannable, and the purpose and usage constraints are front-loaded. A few blocks, notably '[Side effects] None; read-only' and '[Confirmation] Not required', restate annotation content and could be trimmed.

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?

For a read-only two-parameter tool with an output schema, this is thorough: it covers result interpretation per import_item_id/dsers_store_id, how to propagate selected service_id into publish_products_to_stores, and what to do when the user declines. Nothing needed to call or apply it correctly is missing.

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 schema already documents both arrays and the 100-target matrix cap. The description reinforces the pairing semantics (import_list_ids x dsers_store_ids expand to a unique Cartesian product) and stresses copying IDs exactly from list_pre_publish_products and store discovery, adding modest cross-parameter meaning beyond the schema.

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?

The description opens with a specific verb and resource: it 'reads publish-time logistics candidates for each exact Import List product and target-store pair'. It also explicitly bounds what the result is not (not a general store shipping-method list, not the supplier product's catalog, not a freight quote), which separates it cleanly from siblings like list_supplier_product_shipping_methods_and_cost.

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?

Usage is stated in both directions: use only while actively preparing an exact publish_products_to_stores call, once per product-store target, and do not use for standalone/exploratory shipping queries, store/order logistics browsing, publishing, or pricing estimates. The correct alternative for supplier-cost workflows is named explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.