Skip to main content
Glama
Sign In

get4agent

by com.get4agent
OverviewDiscussionsAdmin

Track a Kazpost parcel

track_parcel
Read-onlyIdempotent

Track a Kazakhstan Post parcel by barcode (official track.kazpost.kz): status + route events. Free.

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": {
      "track": "<track>"
    },
    "name": "track_parcel"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesKazpost barcode: 13 characters like RR123456789KZ, or a domestic number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / track / description
      Added value: +"Kazpost barcode: 13 characters like RR123456789KZ, or a domestic number"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine context beyond them: the authoritative data source (track.kazpost.kz), the shape of the response (status + route events) in the absence of an output schema, and the fact that access is free. It does not discuss rate limits or behavior for an unknown barcode, which keeps it from a 5.

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?

One front-loaded sentence: verb and resource first, then scope and return content, then cost. Every clause (barcode, official source, status/events, free) carries information an agent can act on.

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?

For a single-parameter read-only lookup with rich annotations and a fully documented schema, the description covers what the tool does, where the data comes from, and what it returns. Only edge-case behavior (invalid or not-yet-registered barcode) is left implicit, which is a minor gap.

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 coverage is 100% and the single parameter already documents the 13-character format with an example (RR123456789KZ). The description only reinforces 'by barcode' without adding syntax or validation detail, so the baseline 3 applies.

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 (Track) and resource (Kazpost parcel) constrained by barcode lookup, and adds what comes back: status plus route events. No sibling differentiation is offered, but none of the siblings (fx_rates, weather, validate_iin, etc.) overlap with parcel tracking, so the omission costs little.

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?

Usage is implied rather than stated: it is for Kazpost parcels identified by barcode, and the parenthetical points to the official track.kazpost.kz service. There is no explicit when-to-use/when-not guidance and no named alternative, though the sibling list contains no competing tracking tool.

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

All get4agent toolsInspect
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