Skip to main content
Glama
davidgut1982

lore-mcp

by davidgut1982
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_retrieval_telemetry

Retrieve retrieval telemetry rows filtered by query_id, session_id, topic, or recent events. Returns newest entries first.

Instructions

Read retrieval telemetry rows (issue #5). Selector precedence: query_id > session_id > topic > recent. Returns newest-first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
query_idNo
session_idNo
topicNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed17 schema fields changedv0.8.5
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / description
      Removed value: -"Max rows for session_id/topic/recent selectors (default 50, clamped to 500). Ignored for query_id."
    • removedInput schema / properties / limit / maximum
      Removed value: -500
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • addedInput schema / properties / query_id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / query_id / default
      Added value: +null
    • removedInput schema / properties / query_id / description
      Removed value: -"Return the single row for this query_id."
    • removedInput schema / properties / query_id / type
      Removed value: -"string"
    • 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: -"Return rows for this session_id (newest-first)."
    • 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: -"Return rows for this topic (newest-first)."
    • 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
+}
  2. First observedv0.7.0

TDQS

A4/5.0
Behavior4/5

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

Discloses read-only nature, selector precedence, and sorting order (newest-first). With no annotations, it carries the burden well but lacks details on pagination or authentication.

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?

Two concise sentences front-load key information, though the 'issue #5' reference is extraneous.

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?

Provides ordering and precedence but omits description of each parameter's meaning and does not clarify the 'recent' fallback. Adequate but has gaps.

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?

Adds value by explaining selector precedence and hinting at limit, but does not individually describe query_id, session_id, or topic; 0% schema coverage demands more detail.

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?

Description clearly states verb 'Read' and resource 'retrieval telemetry rows', and differentiates from siblings like get_telemetry_stats by mentioning selector precedence.

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?

Provides explicit selector precedence, guiding selection among optional parameters, but does not explicitly state when to use versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidgut1982/lore-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server