Skip to main content
Glama

Register BlueDart Pickup

bluedart_register_pickup
Destructive

Register a pickup with BlueDart at the customer's location using product and area codes. Returns a token number required for later cancellation.

Instructions

Schedule a BlueDart pickup at the customer location via POST /pickup/v1/RegisterPickup. Returns a TokenNumber that is required to cancel the pickup later. AreaCode must match the pickup pincode region (same constraint as waybill OriginArea).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ProductCodeYesBlueDart product code for the pickup (e.g. 'A').
AreaCodeYesBlueDart 3-letter area code matching the pickup pincode.
CustomerCodeYesBlueDart customer code
CustomerNameYes
CustomerAddress1Yes
CustomerAddress2No
ContactPersonNameYes
CustomerPincodeYes6-digit Indian pincode
CustomerTelephoneNumberNoPhone or mobile number (digits, 6-15 chars)
MobileTelNoYes
ShipmentPickupDateYesPickup date as YYYY-MM-DD
ShipmentPickupTimeYesPickup time as HH:MM (24h)
NumberofPiecesYes
WeightofShipmentYesWeight in kg
VolumeWeightYesVolumetric weight in kg
RouteCodeNo99
isToPayShipperNo
Behavior3/5

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

Annotations already provide readOnlyHint=false, destructiveHint=true, idempotentHint=false. The description adds that the tool returns a TokenNumber required for cancellation and that AreaCode must match the pincode region. However, there is a contradiction: description says 'Schedule' (creation) while annotations mark destructiveHint=true, which may mislead.

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 three sentences and front-loaded with key information. While it could omit the API endpoint, it remains compact and relevant.

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?

For a tool with 17 parameters, 13 required, and no output schema, the description is incomplete. It mentions the TokenNumber return but lacks details on success/error handling, anticipated behavior, or further context.

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 coverage is 53%, but the description only adds a repeat of the AreaCode constraint already in the schema. It does not provide additional semantics for the many undocumented parameters.

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 identifies the verb 'Schedule', the resource 'BlueDart pickup', and the specific API endpoint. It also mentions the returned TokenNumber for cancellation, distinguishing it from sibling tool bluedart_cancel_pickup.

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

Usage Guidelines3/5

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

The description implies a use case for creating pickups that can later be cancelled, but it does not explicitly state when to use this tool vs alternatives. No comparison with other pickup-related siblings.

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/nidhiyashwanth/bluedart-mcp-server'

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