Skip to main content
Glama

get_channel_detail_via_channel_name_or_id

Retrieve detailed metadata for a specific Pumble channel using its name, slug, or ID when an explicit channel detail request is made.

Instructions

Get details of a specific channel. Use ONLY when the caller explicitly requests channel metadata.

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": {
      "channelIdentifier": "<channelIdentifier>"
    },
    "name": "get_channel_detail_via_channel_name_or_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdentifierYesChannel name, slug, or ID. If not provided, MUST ASK. DO NOT GUESS.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing about what metadata is returned, whether the call is read-only in side-effect terms, or how it behaves if the identifier doesn't resolve. Beyond the implicit read semantics of "Get", the agent learns no behavioral traits.

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?

Two short sentences with zero padding, and the gating condition is placed after the purpose statement so the agent reads what it does first. Nothing is redundant or buried.

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?

With one required parameter, no annotations, and no output schema, the description is minimally sufficient to invoke the tool correctly. It never indicates what the returned "details" comprise, which leaves a real gap for an agent deciding whether this call answers the caller's question.

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% and the parameter already documents itself as accepting "Channel name, slug, or ID" along with a strong anti-guessing instruction. The description adds no meaning beyond the schema, which is the expected baseline here.

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?

States a specific verb and resource ("Get details of a specific channel"), which is unambiguous against write-oriented siblings like edit_message or delete_message. It does not differentiate from the closest read siblings such as list_channels_only_when_user_calls, but the purpose itself is clear.

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?

"Use ONLY when the caller explicitly requests channel metadata" is a genuine gating condition that tells the agent when not to call it speculatively. It stops short of naming which alternative to use instead (e.g. listing channels vs. fetching one), so it is clear context without explicit routing.

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