Skip to main content
Glama

get_im_channel_by_channel_id

Get IM channel info by ID.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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": {
      "platform": "<platform>",
      "channel_id": "<channel_id>"
    },
    "name": "get_im_channel_by_channel_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform
channel_idYesChannel ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly fails it. It does not say what happens on an unknown channel_id, whether lookup is scoped to a platform, or what 'info' comprises — 'Successful Response' is boilerplate, not behavioral context.

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?

The core sentence is tight and front-loaded with no wasted words. The appended HTTP response section ('### Responses: **200**...') is noise for an agent choosing a tool but is short enough not to obscure the purpose.

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

Completeness1/5

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

With no output schema and no annotations, the description needed to explain what channel info is returned and how failures manifest. It provides none of that, leaving a two-required-parameter lookup tool severely under-described for its complexity.

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%, so the baseline is 3: the two parameters (platform, channel_id) are already documented in the schema. The description only reinforces 'by ID' and adds no meaning about accepted platform values or ID formats.

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 states a specific verb and resource — 'Get IM channel info by ID' — which tells an agent exactly what is retrieved. It does not, however, differentiate this from closely named siblings such as get_im_chat_by_channel_id or search_im_channels, leaving the channel-vs-chat distinction ambiguous.

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?

There is no when-to-use guidance at all: no conditions, no mention of alternatives like search_im_channels for discovery, and no prerequisite or error-path notes. The agent must infer usage purely from the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources