Skip to main content
Glama
Sign In
retail-order-sync-hub

retail-order-sync-hub

by JulioPradenas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

_retry_failed_sync

Force re-enqueue a failed order into the outbox to retry synchronization across all active adapters.

Instructions

Force re-enqueue of an order into the outbox for all active adapters. Scope: outbox.retry. Audited.

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": {
      "order_id": "<order_id>"
    },
    "name": "_retry_failed_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes
api_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It states 'force re-enqueue' and 'audited' but fails to disclose side effects, permissions, rate limits, or whether the operation is reversible.

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 very short at one sentence plus two fragment notes. While concise, it sacrifices completeness and structure, such as listing parameters or describing behavior.

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

Completeness2/5

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

Given the tool has 2 parameters and an output schema (not shown), the description omits crucial details about return values, error handling, and post-conditions, making it incomplete for an agent.

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

Parameters1/5

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

Schema coverage is 0%—the description does not mention either parameter (order_id, api_token). It provides no additional meaning beyond the schema's basic types and defaults.

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 explicitly states the tool's action ('Force re-enqueue of an order into the outbox for all active adapters') and includes scope and audit info, clearly distinguishing it from sibling tools like _replay_dlq_message.

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?

No guidance is given on when to use this tool versus siblings (e.g., _replay_dlq_message, _drain_dlq). The description lacks context about prerequisites or conditions for use.

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