Skip to main content
Glama

⚠️ Orders: click-and-collect (details)

orders_cnc_set_details

Prepares a click-and-collect order by setting the pickup address, booking period, and comment. Sends the details to the buyer.

Instructions

⚠️ Prepares a click-and-collect order and sends the details to the buyer (cnc_set_details, CNC = click-and-collect). Write operation: the seller sets the pickup address, the booking period, and a comment the buyer will see. Call it when the order has an available setCNCDetails action. After handover, confirmation is done via orders_apply_transition (receive) with the buyer's code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAvito order ID.
marketplaceIdYesOrder number in the new Avito system (marketplace).
bookingPeriodYesItem booking period in hours (e.g. 4).
addressNoAddress where the buyer picks up the item (e.g. "Tverskaya Street 3, Moscow").
detailsNoA comment the buyer will receive (e.g. "I can hand over the item from 13:00 to 18:00").
dryRunNov0.7.0: if true — returns a preview of the HTTP request without calling the Avito API. Safe for inspecting exactly what would be done. Default: the value of AVITO_MCP_DRY_RUN_DEFAULT (usually false).
idempotencyKeyNov0.7.0: optional key for duplicate protection. A repeat call with the same key within AVITO_MCP_IDEMPOTENCY_TTL_SEC returns the cached result. The same key with different args returns a conflict error — this is safe by design.
Behavior4/5

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

The description discloses that it is a write operation, sets specific fields (address, booking period, comment), and mentions the dryRun parameter for safe preview. The annotations (readOnlyHint=false, destructiveHint=false) are consistent. No contradictions. The openWorldHint=true flags potential side effects, but the description does not elaborate.

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

Conciseness5/5

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

The description is extremely concise: two sentences plus a brief note. The main action is front-loaded, and every word adds value. No redundancy.

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 7 parameters, 3 required, and no output schema, the description explains the effect (sends details to buyer) and the next step. It provides example values. It could mention error scenarios or state prerequisites, but overall it is sufficiently complete.

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?

The schema has 100% description coverage, so the baseline is 3. The description adds context for 'address' and 'details' with examples, and clarifies that 'bookingPeriod' is in hours. It does not explain 'id' and 'marketplaceId' 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 clearly states the tool's purpose with a specific verb ('prepares') and resource ('click-and-collect order'). It distinguishes from the sibling tool 'orders_apply_transition' by noting the next step after handover. The title warning emoji provides additional context.

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?

The description explicitly specifies when to call the tool: 'Call it when the order has an available setCNCDetails action.' It also mentions the alternative tool for the next step. However, it does not provide explicit conditions for when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elchin92/avito-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server