Skip to main content
Glama

Allegro orders import

allegro_orders_import

[Support desk] Bring the paid Allegro orders still to ship into the Romanian web shop as paid orders (tags allegro, allegro_<pl|cz|sk>, ALLEGRO-), the same road as the Kaufland and Trendyol orders: from the shop they reach Odoo, the invoice and the AWB. Skips orders already in the shop or in Odoo; products are matched by SKU (CDR-START-200x130 → CDRBDS-SLT-START-200 x 130 cm, or a sku_map that is remembered). Tag confirm only when the shop total equals what the buyer paid. Simulated first; runs alone when its action right is auto. Works on: Support desk.

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

Input Schema

NameRequiredDescriptionDefault
accountNoAccount id from list_accounts. Optional when only one account is connected.
sku_mapNo
order_idsNoOnly these Allegro order ids.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses duplicate-skipping behavior, SKU-based product matching with a remembered sku_map, the tag-confirm total-equality condition, and the simulation/action-right execution model. These are meaningful operational traits that an agent would not know from the annotations alone. The write behavior is consistent with readOnlyHint=false and destructiveHint=false.

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

Conciseness3/5

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

The description is front-loaded with the core purpose, but it is a single dense run-on sentence with many parenthetical tags, examples, and conditions. Most content earns its place, yet the structure makes it harder to scan than necessary. It would benefit from splitting purpose, matching rules, and execution behavior into separate sentences.

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?

Given a moderate-complexity import tool with three parameters and an output schema, the description covers the important workflow, skip conditions, SKU matching, tag confirmation, and execution mode. It does not describe error handling or authentication requirements, but those are not essential for correct invocation here. Return values need not be explained because an output schema exists.

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 67%, so the schema already documents some parameters, including account and order_ids. The description adds useful meaning for sku_map by giving a SKU-matching example and noting that mappings are remembered, but it does not explain account or order_ids behavior beyond what the schema provides. This is an adequate but partial enhancement over the structured parameter data.

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 gives a specific verb and resource: bring paid Allegro orders still to ship into the Romanian web shop as paid orders. It clearly scopes the operation to Allegro orders and distinguishes it from the analogous Kaufland and Trendyol imports. It does not explicitly name a sibling tool to use instead, but the purpose itself is unambiguous.

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

Usage Guidelines4/5

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

It explains the operational context: paid orders still to ship, orders already present in the shop or Odoo are skipped, and tag confirmation only happens when totals match. It also notes that the action is simulated first and runs alone when its action right is auto. It stops short of explicit when-not-to-use guidance or naming an alternative tool for other order-import scenarios.

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.

Resources