Connhex MCP Server

Official

by compiuta-origin

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List Thing Channels

get_thing_channels

Read-only

Retrieve channels attached to a device using its unique identifier. Supports pagination and filtering by connection state.

Instructions

List the channels connected to a specific thing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "thing_id": "<thing_id>"
    },
    "name": "get_thing_channels"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max items to return.
`offset`	No	Number of items to skip.
`thing_id`	Yes	UUID of the thing.
`connected`	No	Filter by connection state.

Output Schema

Name	Required	Description
`limit`	No	Page size used.
`total`	No	Total number of matching channels.
`offset`	No	Number of items skipped.
`channels`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description adds minimal behavioral information. It does not mention pagination, filtering capabilities, or any caveats beyond the basic purpose.

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?

Description is a single, efficient sentence that directly states the purpose without extraneous words. Follows principle of front-loading key information.

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

Completeness2/5

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

Despite having an output schema and 4 parameters, the description does not mention pagination (limit/offset) or filtering (connected state). The minimal description leaves the agent guessing about important features, reducing completeness.

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%, with all parameters described. The tool description does not add any extra meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 'List the channels connected to a specific thing', using a specific verb and resource. It distinguishes from sibling tools like 'list_things' or 'read_thing_messages' by focusing on channels per thing.

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 implies usage context (listing channels for a thing) but provides no guidance on when to use this tool versus alternatives like 'read_channel_messages' or 'get_thing'. No exclusions or when-not-to-use hints provided.

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