Skip to main content
Glama

Trackkr.app - Parcel log for apartments

release_parcel_with_signature

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.

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": {
      "businessId": "<businessId>",
      "parcelId": "<parcelId>",
      "pickedUpBy": "<pickedUpBy>"
    },
    "name": "release_parcel_with_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorNoAudit identity of the staff user or AI agent releasing the parcel.
parcelIdYesFirestore parcel document ID under businesses/{businessId}/parcels/{parcelId}.
businessIdYesTenant business identifier owning the parcel (1-128 alphanumeric/dash/underscore chars).
pickedUpByYesFull name of the resident or authorized person who signed for and collected the parcel (1-120 characters).
datePickedUpNoOptional pickup date in YYYY-MM-DD format (defaults to current UTC date).
releaseNotesNoOptional audit note recorded in PARCEL_RELEASED telemetry (maximum 500 characters).
signatureUrlNoTrusted HTTPS Firebase Cloud Storage URL of the captured recipient signature PNG. Either signatureUrl or signatureBase64 must be supplied.
timePickedUpNoOptional pickup time string (e.g. "4:15 PM", defaults to current UTC time).
signatureBase64NoBase64-encoded PNG signature image (up to 2MB decoded). Automatically uploaded to businesses/{businessId}/signatures/{parcelId}.png when signatureUrl is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well on side effects: it discloses a state mutation, an audit record, an external Firebase Storage write, and telemetry emission. It omits permissions/auth requirements, idempotency and failure behavior, which keeps it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that leads with the primary state change and then chains the secondary effects in order. No filler or repetition, though the run-on structure would scan better as a short effect list.

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

Completeness3/5

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

For a 9-parameter mutation with a nested actor object, no annotations and no output schema, the description explains the write flow but leaves out preconditions (required current parcel state), authorization expectations and error/conflict behavior. Return values need not be covered since no output schema exists.

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%, including the mutually-exclusive signatureUrl/signatureBase64 pair and format constraints, so the schema does the heavy lifting. The description mentions the recipient name, timestamp and signature artifact conceptually but adds no syntax or format detail beyond what is already documented.

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?

The description states a specific verb+resource and enumerates the concrete effects: parcel state moves to Picked Up, timestamp and recipient are recorded, the signature PNG is stored, and a PARCEL_RELEASED event is emitted. This is clearly distinguishable from the intake and listing siblings by lifecycle stage, though it never names an alternative to differentiate explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use framing: nothing says which prior parcel state this release requires, when to prefer signatureUrl over signatureBase64 workflow-wise, or why an agent would call this rather than log_incoming_parcel. The reader can only infer usage from the effects described.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources