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

retail-order-sync-hub

by JulioPradenas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

_find_failed_orders

Identify orders that were created in your system but never synced to any marketplace, helping you resolve synchronization failures.

Instructions

Find orders that were created but never successfully synced to a marketplace.

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

Input Schema

NameRequiredDescriptionDefault
sinceNo24h
api_tokenNo
marketplaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 disclose behavioral traits. It only hints at a read operation ('Find') but does not confirm whether it is read-only, requires authentication (beyond the api_token parameter), or has rate limits or other constraints.

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?

The description is a single concise sentence with no wasted words. However, it omits important details about parameters and usage, so it does not fully earn its place in terms of completeness.

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?

The tool has an output schema, so return values need not be explained. However, the three parameters are undocumented in both schema and description. The description lacks context on how to use the tool effectively, leaving moderate gaps.

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 description coverage is 0%, yet the description does not explain any parameters. The meanings of 'since,' 'api_token,' and 'marketplace' are left to inference. This is insufficient compensation for the lack of schema descriptions.

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 clearly states the verb 'Find' and the resource 'orders that were created but never successfully synced to a marketplace.' It implicitly distinguishes from sibling tools like _get_order_status and _retry_failed_sync by specifying the failure condition, but does not explicitly differentiate.

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 on when to use this tool versus alternatives. It does not mention prerequisites, context, or exclusions. The description only states what it does without any usage advice.

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