NetCourier Parcel Tracking

get_delivery_proof

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.

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": {
      "system": "<system>",
      "trackingNo": "<trackingNo>",
      "postcode": "<postcode>"
    },
    "name": "get_delivery_proof"
  }
}

Input Schema

Name	Required	Description
`system`	Yes	Name of the tracking system, e.g. 'sparkle'. Lower-case sub-domain name only.
`postcode`	Yes	The collection or delivery postcode for this parcel, e.g. 'W14 0HN'
`trackingNo`	Yes	The parcel tracking number, e.g. EX10004130651

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully states the required inputs and the ask-don't-guess rule for a missing postcode, but says nothing about permissions, what happens when no POD exists, or error/empty-result behavior in a courier lookup.

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?

Front-loaded with purpose, then usage triggers, then input requirements and the missing-postcode rule. Every sentence carries information; only the parenthetical 'proof of delivery / POD' is mildly redundant.

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 no output schema, the description compensates by naming the returned fields (location, signature source). All three required params are covered and the missing-input workflow is handled, leaving only failure/empty-result handling unstated.

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?

Schema description coverage is 100%, so all three parameters are already documented, including examples for system, postcode, and trackingNo. The description restates the required set and clarifies postcode means 'the collection or delivery postcode for that parcel', a marginal addition over the schema.

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?

States a specific verb+resource ('Get proof-of-delivery details for a parcel') and enumerates what is returned (delivery/collection location and recipient signature). It is clearly separable from get_parcel_tracking, though it never names that sibling to sharpen the contrast.

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?

Gives concrete trigger conditions ('where a parcel was delivered', 'who signed for it', 'POD') and a fallback behavior when the postcode is unknown ('ask the user rather than guessing'). It does not name alternatives such as get_parcel_tracking for status-only queries, so routing guidance is clear but not exhaustive.

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

All NetCourier Parcel Tracking tools Inspect

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.