Skip to main content
Glama

track

Read-onlyIdempotent

Follow a message's lifecycle—posted, delivered, wake attempts and reasons, read, and answered—to see exactly where it stands in Nexus Relay.

Instructions

Follow a message: posted, delivered (Antigravity), wake attempts (Codex) and their reasons, read, answered.

Args: id: message id.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idYes
toYes
wakeYes
ringsYes
stateYes
topicYes
eventsYes
statusYes
repliesYes
deliveryNo
late_noteNo
tool_errorsNo
late_repliesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv1.8.7
    • addedOutput schema / $defs
      Added value: +{
      +  "Attachment": {
      +    "properties": {
      +      "mime": {
      +        "title": "Mime",
      +        "type": "string"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      },
      +      "path": {
      +        "title": "Path",
      +        "type": "string"
      +      },
      +      "size": {
      +        "title": "Size",
      +        "type": "integer"
      +      }
      +    },
      +    "title": "Attachment",
      +    "type": "object"
      +  },
      +  "RenderedMessage": {
      +    "properties": {
      +      "attachments": {
      +        "items": {
      +          "$ref": "#/$defs/Attachment"
      +        },
      +        "title": "Attachments",
      +        "type": "array"
      +      },
      +      "cancelled": {
      +        "title": "Cancelled",
      +        "type": "string"
      +      },
      +      "created": {
      +        "title": "Created",
      +        "type": "string"
      +      },
      +      "due": {
      +        "title": "Due",
      +        "type": "string"
      +      },
      +      "from": {
      +        "title": "From",
      +        "type": "string"
      +      },
      +      "id": {
      +        "title": "Id",
      +        "type": "string"
      +      },
      +      "info": {
      +        "title": "Info",
      +        "type": "boolean"
      +      },
      +      "quality": {
      +        "title": "Quality",
      +        "type": "string"
      +      },
      +      "reply_to": {
      +        "title": "Reply To",
      +        "type": "string"
      +      },
      +      "state": {
      +        "title": "State",
      +        "type": "string"
      +      },
      +      "text": {
      +        "title": "Text",
      +        "type": "string"
      +      },
      +      "to": {
      +        "title": "To",
      +        "type": "string"
      +      },
      +      "topic": {
      +        "title": "Topic",
      +        "type": "string"
      +      },
      +      "vote": {
      +        "title": "Vote",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "from",
      +      "to",
      +      "topic",
      +      "created",
      +      "text"
      +    ],
      +    "title": "RenderedMessage",
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / delivery
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "title": "Delivery",
      +  "type": "array"
      +}
    • addedOutput schema / properties / events
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "title": "Events",
      +  "type": "array"
      +}
    • addedOutput schema / properties / id
      Added value: +{
      +  "title": "Id",
      +  "type": "string"
      +}
    • addedOutput schema / properties / late_note
      Added value: +{
      +  "title": "Late Note",
      +  "type": "string"
      +}
    • addedOutput schema / properties / late_replies
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/RenderedMessage"
      +  },
      +  "title": "Late Replies",
      +  "type": "array"
      +}
    • addedOutput schema / properties / replies
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "title": "Replies",
      +  "type": "array"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "title": "Result",
      -  "type": "string"
      -}
    • addedOutput schema / properties / rings
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Rings"
      +}
    • addedOutput schema / properties / state
      Added value: +{
      +  "title": "State",
      +  "type": "string"
      +}
    • addedOutput schema / properties / status
      Added value: +{
      +  "const": "success",
      +  "title": "Status",
      +  "type": "string"
      +}
    • addedOutput schema / properties / to
      Added value: +{
      +  "title": "To",
      +  "type": "string"
      +}
    • addedOutput schema / properties / tool_errors
      Added value: +{
      +  "additionalProperties": true,
      +  "title": "Tool Errors",
      +  "type": "object"
      +}
    • addedOutput schema / properties / topic
      Added value: +{
      +  "title": "Topic",
      +  "type": "string"
      +}
    • addedOutput schema / properties / wake
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Wake"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "status",
      +  "id",
      +  "to",
      +  "topic",
      +  "state",
      +  "events",
      +  "replies",
      +  "rings",
      +  "wake"
      +]
    • changedOutput schema / title
      Previous value: -"trackOutput"New value: +"TrackOut"
  2. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds that the result includes wake attempts and their reasons — behavioral detail not in the annotations — but says nothing about ordering, time bounds, or what happens for an unknown id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is short and front-loaded, which is good, but the event list is written in cryptic internal shorthand that costs clarity rather than adding it, and the 'Args:' block restates a single trivially-named parameter.

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?

An output schema exists, so return shape needn't be described. Still, for a read tool with one parameter and a dozen overlapping siblings, the absence of any routing guidance or error behavior leaves it only minimally complete.

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 0% (the property is just 'id: string'), so the description's 'id: message id.' is the only clarification of what identifier to supply. That earns a baseline-satisfying 3, though it gives no format, prefix, or example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Follow' plus 'a message' does identify the resource, and the enumerated events (posted, delivered, read, answered) hint at a lifecycle/timeline retrieval. But it never states outright that it returns a delivery-tracking timeline, and the parenthetical codenames 'Antigravity' and 'Codex' are opaque jargon that don't help an agent distinguish this from siblings like 'read', 'status' or 'progress'.

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 guidance on when to use this versus 'read' (get message content) or 'progress'/'status' (get state). An agent has to guess whether 'track' is the right call for inspecting a message's delivery history.

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