touch-browser

Overview Schema Source Related Servers Discussions Admin

Recent Pilot Telemetry

tb_telemetry_recent

Retrieve recent pilot telemetry events from the current runtime. Use the limit parameter to control the number of events returned.

Instructions

Return recent pilot telemetry events for the current runtime.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	The maximum number of recent telemetry events to return.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	Yes
`events`	Yes
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Jun 12, 2026

addedInput schema / properties / limit / description

Added value: +"The maximum number of recent telemetry events to return."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "events": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "currentUrl": {
+            "type": "string"
+          },
+          "operation": {
+            "type": "string"
+          },
+          "payload": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "policyDecision": {
+            "type": "string"
+          },
+          "policyProfile": {
+            "type": "string"
+          },
+          "recordedAtMs": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "riskClass": {
+            "type": "string"
+          },
+          "sessionId": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "surface": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "operation",
+          "recordedAtMs",
+          "status",
+          "surface"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "result": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "currentUrl": {
+            "type": "string"
+          },
+          "operation": {
+            "type": "string"
+          },
+          "payload": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "policyDecision": {
+            "type": "string"
+          },
+          "policyProfile": {
+            "type": "string"
+          },
+          "recordedAtMs": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "riskClass": {
+            "type": "string"
+          },
+          "sessionId": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "surface": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "operation",
+          "recordedAtMs",
+          "status",
+          "surface"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "limit",
+    "events",
+    "result"
+  ],
+  "type": "object"
+}

First observedv0.1.11Apr 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are present, so the description must bear the full burden of behavioral disclosure. It fails to explain what 'recent' means (time window), what events are included, or any side effects. The tool could be read-only but no confirmation.

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?

The description is extremely concise, containing only one sentence. While this is efficient, it sacrifices necessary detail, making it borderline under-specified.

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

Completeness2/5

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

Given the presence of an output schema (inferred from context signals) and a sibling telemetry summary tool, the description is incomplete. It does not mention the output format, how events are ordered, or how this differs from tb_telemetry_summary.

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% for the limit parameter, so baseline is 3. The description adds no additional meaning beyond the schema; it could clarify that 'recent' implies a default time window or that limit caps the number of events.

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 clearly states it returns recent pilot telemetry events, using a specific verb and resource. However, it does not distinguish itself from sibling tb_telemetry_summary, which likely provides a summary rather than raw events.

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?

No guidance is provided on when to use this tool versus alternatives like tb_telemetry_summary. There are no prerequisites or context on the 'current runtime' scope.

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