Skip to main content
Glama

LiveDataLink

by io.github.blackboxfoundry

package_track

Read-onlyIdempotent

Identify the likely carrier for a package tracking number and return a direct tracking link. Supports common USPS, UPS, FedEx, DHL, and Amazon formats. Live delivery status, location, estimated arrival, and history are not fetched by this tool yet; open the returned carrier link for the current shipment record. Just paste the tracking number - the carrier is detected automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tracking_numberYesPackage tracking number from any carrier

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already show readOnlyHint=true and idempotentHint=true, and the description adds meaningful behavioral detail: it returns a carrier link rather than live shipment data, and it relies on automatic carrier detection. The stated limitation about not fetching delivery status is particularly valuable beyond the annotations.

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 compact and well-structured: it opens with the core function, then adds scope, limitations, and usage guidance in a natural order. Every sentence earns its place without repetition or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with rich annotations, the description fully covers what the tool does, what it returns, and what it intentionally does not provide. Since there is no output schema, the explicit statement that it returns a direct tracking link is essential and sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents the single tracking_number parameter with 100% coverage, so the baseline is 3. The description adds value by explaining that the carrier is detected automatically and listing supported carrier formats, which clarifies what kinds of input are valid beyond the schema's generic phrasing.

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 a specific purpose: identify the likely carrier for a tracking number and return a direct tracking link. It also scopes the tool to common USPS, UPS, FedEx, DHL, and Amazon formats, making its function unambiguous and distinct from broader package-lookup tools.

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 gives clear usage context: paste a tracking number and the tool auto-detects the carrier. It also explicitly warns that live delivery status, location, and history are not provided, so an agent knows not to use this tool for real-time shipment updates. It does not name an alternative tool, but no obvious sibling provides the same function.

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

All LiveDataLink toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

Several tool clusters overlap heavily—company due-diligence and risk tools (counterparty_risk_score, company_trust_check, entity_dossier, issuer_diligence_dossier, resolve_entity, entity_resolve), carrier vetting tools, sanctions screening tools, and recall tools all have subtle boundary distinctions. While descriptions are detailed, an agent navigating 294 tools will frequently struggle to pick the right one.

Naming Consistency3/5

Most tools follow a readable snake_case domain-prefix pattern (fdic_, edgar_, sanctions_, congress_), which helps. However, verb placement is inconsistent—search_available_datasets vs cdc_dataset_query, resolve_entity vs entity_resolve—and synonyms like search, lookup, get, detail, fetch, and status are used interchangeably.

Tool Count1/5

294 tools is an extreme number for a single MCP server, far beyond what an agent can reliably hold in context or select from accurately. The presence of tool-group discovery helpers mitigates but does not solve the fundamental scale problem.

Completeness4/5

The data breadth is genuinely extensive, covering finance, health, legal, real estate, transportation, energy, cyber, education, and many other domains, often with generic query fallbacks. Still, some capabilities are shallow or incomplete—package tracking stops at a link, property tools are demo-only in places, and caselaw coverage is limited—so it is not a fully complete surface.

Resources