Skip to main content
Glama

LogNexus Telemetry: Local performance and ROI cost report

lognexus_telemetry

Inspect, enable, disable, or clear local telemetry metrics, review zero-PII payloads, and generate markdown reports to measure subtask duration, Git Notes coverage, and cost savings without uploads.

Instructions

Inspect local telemetry status, enable strictly local performance metrics (zero network calls), disable tracking, inspect the zero-PII local payload, generate telemetry markdown reports, or clear the metrics store. Use when measuring subtask duration, Git Notes coverage and estimated cost savings. Not for any form of upload: telemetry is local-only, stored in .lognexus/telemetry.json, and no data leaves the working directory.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "report"
    },
    "name": "lognexus_telemetry"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoTelemetry action to perform. Defaults to 'status'.
outputPathNoTarget file path when generating report (defaults to .lognexus/telemetry.md).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.6
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "action": "report"
      +  }
      +]
    • removedInput schema / properties / acceptTerms
      Removed value: -{
      -  "description": "Explicit acceptance of telemetry terms (required when share is true).",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / share
      Removed value: -{
      -  "description": "When action is 'enable', set to true to enable anonymous community telemetry.",
      -  "type": "boolean"
      -}
  2. First observedv0.1.0

TDQS

A4.3/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 burden and does well: it discloses zero network calls, zero-PII payloads, the exact storage location (.lognexus/telemetry.json), and that data never leaves the working directory. It implies 'clear' removes the metrics store but does not state whether that is irreversible or what happens to concurrent sessions, 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?

The action inventory is front-loaded and the usage/privacy constraints follow in two tight sentences with no filler. The initial sentence is long but every clause maps to a distinct action or guarantee.

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

Completeness4/5

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

For a six-action mutation tool with no annotations and no output schema, the description supplies privacy posture, storage path, and purpose. The remaining gaps — what each action returns and whether 'clear' is recoverable — are modest but real given the destructive 'clear' option.

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?

Schema coverage is 100%, so the baseline would be 3; the description earns above that by giving each enum action operational meaning — 'enable strictly local performance metrics', 'inspect the zero-PII local payload', 'clear the metrics store' — beyond the raw enum labels. outputPath semantics are left entirely to the schema, which already documents the default.

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

Purpose5/5

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

The description names a specific resource (local telemetry) and enumerates every operation — status, enable, disable, inspect, report, clear — in verb+object form. It also distinguishes itself from siblings implicitly by scoping to performance/ROI metrics stored locally, rather than state, audit, or Git operations. An agent can tell what this tool does without opening the schema.

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

Usage Guidelines4/5

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

It gives clear trigger conditions ('Use when measuring subtask duration, Git Notes coverage and estimated cost savings') and an explicit exclusion ('Not for any form of upload'). The gap is that no sibling tool is named as an alternative, so routing between lognexus_status, lognexus_audit, and this tool is left to inference.

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