lore-mcp

get_telemetry_stats

Aggregate retrieval telemetry stats including totals, feedback coverage, requery count, average score, and timestamps, optionally scoped by session or topic.

Instructions

Aggregate retrieval telemetry stats (issue #5): totals, feedback coverage, requery count, average score, oldest/newest timestamps. Optionally scoped by session_id and/or topic.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`session_id`	No
`topic`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.8.5May 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / session_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / session_id / default
```
Added value: +null
```

removedInput schema / properties / session_id / description

Removed value: -"Restrict stats to this session_id (optional)."

removedInput schema / properties / session_id / type
```
Removed value: -"string"
```

addedInput schema / properties / topic / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / topic / default
```
Added value: +null
```

removedInput schema / properties / topic / description

Removed value: -"Restrict stats to this topic (optional)."

removedInput schema / properties / topic / type
```
Removed value: -"string"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv0.7.0May 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations provided, so the description carries full burden. It discloses the aggregate behavior and optionally scoping, but does not mention side effects, performance, or read-only status. Basic transparency, but could add more context.

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?

Two sentences, each delivering distinct, relevant information: first sentence lists the returned stats, second sentence explains optional filtering. No redundancy or fluff.

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?

The description lists all key output fields and parameter purpose, which is sufficient given the output schema exists. The tool is simple (2 optional params, no required params) and the description covers the main functionality. Minor omission: not explicitly stating it's read-only, but implied.

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%, but the description states parameters are for scoping ('Optionally scoped by session_id and/or topic'), adding meaning beyond the schema. However, it lacks details on expected formats or constraints, only partially compensating for low coverage.

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 the verb 'aggregate' and the resource 'retrieval telemetry stats', listing specific computed fields. It does not explicitly differentiate from sibling 'get_retrieval_telemetry', but the name and content suggest it's an aggregate variant.

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

Usage Guidelines3/5

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

The description mentions optional scoping by session_id and/or topic, implying when to filter. However, it lacks explicit guidance on when to use this tool versus alternatives like get_retrieval_telemetry, and no when-not-to-use information.

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