Skip to main content
Glama
Sign In

NetCourier Parcel Tracking

by io.github.zahidul-alam-m4
OverviewDiscussionsAdmin

Server Details

MCP server for tracking parcels using the NetCourier tracking service.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
zahidul-alam-m4/tracking-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct need: current tracking status/history (get_parcel_tracking), proof-of-delivery specifics (get_delivery_proof), and configuration discovery (list_tracking_systems). The descriptions explicitly cross-reference each other, telling the agent to use get_delivery_proof when delivery location or signature is requested, which removes the main source of overlap.

Naming Consistency5/5

All three tools follow a clean verb_noun snake_case pattern (get_delivery_proof, get_parcel_tracking, list_tracking_systems). Verbs are used consistently and meaningfully, with no mixed conventions.

Tool Count4/5

Three tools is on the thin side but well-scoped for a narrow, read-only parcel-tracking domain. Each earns its place, though a slightly broader surface could justify a few more tools.

Completeness4/5

The surface covers the core lifecycle reads for parcel tracking: system discovery, tracking status/events, and proof of delivery. Gaps like bulk/multi-parcel lookup or event-only queries exist but are minor for the stated purpose.

Available Tools

3 tools
get_delivery_proofAInspect

Get proof-of-delivery details for a parcel: delivery/collection location and the recipient's signature, from a courier system. Use when the user asks where a parcel was delivered, who signed for it, or for proof of delivery / POD. Requires the system name, the tracking number, and a postcode (the collection or delivery postcode for that parcel) - if the postcode is not given or known from earlier in the conversation, ask the user for it rather than guessing.

Inputs: system (required), postcode (required), trackingNo (required).

get_parcel_trackingAInspect

Get the latest tracking information / status / event history of a parcel (consignment) from a courier system. Use when the user asks about a parcel, shipment, consignment or tracking number and mentions a system name (e.g. 'sparkle'). Extract the system name and the tracking number from the user's message. If the user separately asks for the delivery location or the signature/proof of delivery, use the get_delivery_proof tool instead (or afterwards) - it needs a postcode as well.

Inputs: system (required), trackingNo (required).

list_tracking_systemsAInspect

List the tracking systems that are explicitly configured, and the default URL pattern used for other system names.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources