Skip to main content
Glama
compiuta-origin

Connhex MCP Server

Official

Read Channel Messages

read_channel_messages
Read-only

Retrieve messages from a Connhex IoT channel using its channel ID. Supports filtering by time range, publisher, metric name, format, and decimation.

Instructions

Read messages from a Connhex IoT channel by its channel ID.

Use this when you already have a channel ID. To go from a device's business identifier (serial, etc.) to messages, prefer read_thing_messages, which resolves the channel ID for you from a thing ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dsNoDecimation granularity, format "<number><s|m|h|d|w|M|y>" (e.g. "5m", "1h", "1d"). When set, the upstream service buckets messages and aggregates them with dsf. Only applies to SenML-based formats ("messages", "params", "metrics").
dsfNoAggregation function for decimation: max, min, avg, sum, stddev, variance. Defaults to "avg" upstream.
dsvNoDecimation value type: "v" for numeric SenML values, "vb" for boolean. Defaults to "v" upstream.
nameNoSenML name (metric URN) filter. Only applies to SenML-based formats ("messages", "params", "metrics"). Ignored for "infos".
to_sNoEnd time in Unix epoch seconds. Always provide from_s and to_s together when the requested time range is known; this drastically speeds up database queries. The integer part represents whole seconds; the fractional part provides sub-second precision (e.g. 1744243200.183767).
limitNoMax messages to return (upstream max is 1500).
formatNoWhich Connhex Message Policy (CMP) component to read. "messages" (default): time-series sensor data collected during operation (e.g. temperature, pressure). SenML format. Most common format — use for actual measurements or telemetry. "params": runtime-editable configuration parameters of the device (e.g. operating mode, thresholds). SenML format. Use to inspect or verify device settings. "infos": static or rarely-changing device metadata sent at boot or after firmware updates (e.g. serial number, firmware version, hardware revision). JSON format (not SenML). Use to identify or describe the device. name, ds, dsf, and dsv do not apply to this format. "metrics": internal device performance indicators (e.g. CPU usage, RAM consumption, uptime). SenML format. Use for device health monitoring and diagnostics.messages
from_sNoStart time in Unix epoch seconds. Always provide from_s and to_s together when the requested time range is known; this drastically speeds up database queries. The integer part represents whole seconds; the fractional part provides sub-second precision (e.g. 1744243200.183767).
offsetNoPagination offset.
publisherNoPublisher UUID filter.
channel_idYesUUID of the channel.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYes
totalYes
offsetYes
messagesNo
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, indicating safe read-only behavior. The description adds minimal behavioral context beyond the obvious (reading messages). No contradiction, but it doesn't elaborate on pagination or other behaviors.

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 with two sentences. The first sentence states the core purpose, and the second provides usage guidance. No wasted words, effectively front-loaded.

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?

Given the tool's complexity (11 parameters), the presence of an output schema, and rich parameter descriptions in the schema, the description is adequate. It covers the primary use case and differentiation, though it could optionally mention time range optimization mentioned in the schema.

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 description coverage is 100%, so baseline is 3. The description does not add additional meaning to parameters beyond what the schema already provides. It only mentions channel_id in the text.

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 'Read messages from a Connhex IoT channel by its channel ID' with a specific verb and resource. It also explicitly distinguishes from the sibling tool read_thing_messages, making the purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit guidance: 'Use this when you already have a channel ID' and directs to read_thing_messages for device business identifiers. This clearly sets when to use this tool vs 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/compiuta-origin/connhex-tools'

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