touch-browser

Overview Schema Source Related Servers Discussions Admin

Pilot Telemetry Summary

tb_telemetry_summary

Retrieve the aggregated pilot telemetry summary for the current runtime to analyze system performance and usage patterns.

Instructions

Return the aggregated pilot telemetry summary for the current runtime.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes
`summary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": false,
+      "properties": {
+        "dbPath": {
+          "type": "string"
+        },
+        "distinctSessionCount": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "latestRecordedAtMs": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "operationCounts": {
+          "additionalProperties": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "type": "object"
+        },
+        "statusCounts": {
+          "additionalProperties": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "type": "object"
+        },
+        "surfaceCounts": {
+          "additionalProperties": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "type": "object"
+        },
+        "totalEvents": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "dbPath",
+        "distinctSessionCount",
+        "latestRecordedAtMs",
+        "operationCounts",
+        "statusCounts",
+        "surfaceCounts",
+        "totalEvents"
+      ],
+      "type": "object"
+    },
+    "summary": {
+      "additionalProperties": false,
+      "properties": {
+        "dbPath": {
+          "type": "string"
+        },
+        "distinctSessionCount": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "latestRecordedAtMs": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "operationCounts": {
+          "additionalProperties": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "type": "object"
+        },
+        "statusCounts": {
+          "additionalProperties": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "type": "object"
+        },
+        "surfaceCounts": {
+          "additionalProperties": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "type": "object"
+        },
+        "totalEvents": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "dbPath",
+        "distinctSessionCount",
+        "latestRecordedAtMs",
+        "operationCounts",
+        "statusCounts",
+        "surfaceCounts",
+        "totalEvents"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result",
+    "summary"
+  ],
+  "type": "object"
+}

First observedv0.1.11Apr 15, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided. The description does not disclose whether the operation is read-only, idempotent, requires authentication, or has side effects. Minimal behavioral context beyond the basic action.

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?

Single sentence, no fluff. Perfectly concise and front-loaded.

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?

Given zero parameters and an output schema (not provided but exists), the description is somewhat vague about what 'aggregated' means or what time period it covers. It suffices for basic understanding but lacks detail.

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 input schema has zero parameters, so schema description coverage is 100%. The description adds no parameter details, but none are needed. Baseline 4 applies.

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 an aggregated pilot telemetry summary for the current runtime. The verb 'Return' and resource are unambiguous, but 'aggregated' and 'current runtime' could be more precisely defined.

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 on when to use this tool versus alternatives like 'tb_telemetry_recent'. No context on prerequisites or exclusions provided.

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