Skip to main content
Glama
Younes-Alaoui-Ismaili

mcp-live-telemetry

Get telemetry

get_telemetry
Read-onlyIdempotent

Retrieve time-ordered sensor readings for any device over a specified time window, with optional pagination and step size.

Instructions

Return time ordered sensor readings for one device across a time window.

Inputs: device_id (required), start and end (epoch ms, optional, default last 15 minutes), step_ms (default 30000), limit and offset for pagination, response_format. Returns { device_id, start, end, step_ms, total, count, offset, has_more, next_offset?, readings: [{ timestamp, temperature_c, vibration_mm_s, state }] }. Read only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoWindow end (epoch ms). Defaults to now.
limitNoMax readings returned (pagination).
startNoWindow start (epoch ms). Defaults to end minus 15 minutes.
offsetNoReadings to skip (pagination).
step_msNoSampling step in milliseconds (1000 to 3600000).
device_idYesDevice id, for example 'press-01'. Call list_devices for valid ids.
response_formatNoText output format: 'markdown' (default, human readable) or 'json'.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYes
countYes
startYes
totalYes
offsetYes
step_msYes
has_moreYes
readingsYes
device_idYes
next_offsetNo
Behavior4/5

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

The description adds significant behavioral context beyond annotations: it confirms read-only nature ('Read only'), explains pagination details (has_more, next_offset), and specifies defaults for time window and step. Annotations already indicate readOnlyHint, idempotentHint, and non-destructive, but the description enriches with concrete runtime behavior.

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?

The description is extremely concise: three sentences covering purpose, inputs, and output. Front-loads the primary action, then efficiently enumerates parameters and return shape. No wasted words.

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 tool with 7 parameters and an output schema, the description is quite complete: it specifies all inputs with defaults, explains pagination, and details the return object including nested readings. Minor omission: the meaning of readings fields like 'state' could be elaborated, but output schema existence mitigates this.

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%, with each parameter having a description in the schema. The tool description summarizes parameters but does not add substantial new meaning beyond the schema. It lists the key parameters and defaults but lacks additional semantics like edge cases or constraints.

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 clearly states the tool's purpose: 'Return time ordered sensor readings for one device across a time window.' It uses a specific verb (Return) and resource (sensor readings), and distinguishes it from sibling tools like list_devices (lists devices) and get_anomalies (returns anomalies).

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?

The description does not provide explicit guidance on when to use this tool versus alternatives, nor does it state when not to use it. It only describes the tool's function without contextualizing its place among siblings like list_devices or get_anomalies.

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/Younes-Alaoui-Ismaili/mcp-live-telemetry'

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