digikala-mcp

Get Cart Operation

get_cart_operation

Read-only

Inspect a journaled cart plan or replacement for the connected account, covering prepared, executing, uncertain, and terminal states without sending a mutation.

Instructions

Inspect a journaled plan/replacement owned by the connected desktop account.

Includes prepared, executing, uncertain and terminal states; does not send a mutation.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "get_cart_operation"
  }
}

Input Schema

Name	Required	Description	Default
`operation_id`	Yes

Output Schema

Name	Required	Description	Default
`kind`	Yes
`plan`	No
`state`	Yes
`reason`	No
`result`	No
`expired`	No
`operation_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior: which lifecycle states are returned (prepared, executing, uncertain, terminal) and the reassurance that no mutation is sent, which clarifies what an 'operation' inspection means.

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?

Two tight sentences, front-loaded with the primary action and followed by the state coverage. No filler, though the second sentence could integrate more economically.

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?

With an output schema present, return values need not be explained, and annotations cover safety. State coverage is described, so the only real gap is the undocumented operation_id, which is minor for a single-parameter read.

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?

There is one parameter (operation_id) with 0% schema description coverage; the strict pattern ^[a-f0-9]{32}$ is the only guidance. The description never mentions the parameter or its expected format, so it does not compensate for the documentation gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb ('inspect') and an object ('journaled plan/replacement'), but 'journaled plan/replacement' is unusual jargon an agent cannot fully map to a concrete resource. The desktop-vs-account distinction from the sibling get_account_cart_operation is only hinted at ('connected desktop account'), never made explicit.

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 statement of when to use this versus alternatives such as get_account_cart_operation or reconcile_cart_operation. The only usage cue is the implicit 'inspect state,' which an agent must infer.

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

Deploy Server