Trackkr MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USE_MOCK_OCR | No | Set to `true` during local staging to bypass paid Google Cloud Vision API billing counters. | |
| FIREBASE_CONFIG_JSON | Yes | Path to your authorized Firebase service account credentials (or stringified JSON). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pending_parcelsB | Fetches the current ledger of uncollected packages, highlights aging stats (5+ days), enriches each with occupant contact preferences and notification/telemetry history, and returns structured JSON context. |
| log_incoming_parcelB | Accepts parsed text from Google Cloud Vision OCR label scans and/or a trusted Firebase Storage photoUrl, cross-references internal Firestore unit listings, enforces a 4-hour idempotent lock on (trackingNumber + unitId), and schedules automated email alerts via SendGrid. |
| release_parcel_with_signatureB | Updates parcel state to Picked Up, records the pickup timestamp and recipient name, securely saves the digital signature PNG layout to Firebase Storage, and emits a PARCEL_RELEASED telemetry event. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct parcel lifecycle stage: viewing pending parcels, logging incoming parcels, and releasing parcels with signature. There is no meaningful overlap in purpose or resource, so an agent can easily select the right tool.
All tool names use snake_case with a leading verb and a parcel-related noun (get_pending_parcels, log_incoming_parcel, release_parcel_with_signature). The pattern is predictable, and the third tool's modifier does not disrupt readability.
Three tools is lean but reasonable for a focused intake-to-release workflow. It is slightly under-scoped for a parcel-tracking domain that likely benefits from additional query and update operations.
The core lifecycle is covered: log incoming, list pending, and release with signature. However, there are notable gaps such as getting a parcel by ID, listing full history/all parcels, updating parcel details, canceling/deleting, and managing notifications or units.