Skip to main content
Glama

Get channel capabilities

mynahcast_get_channel_capabilities
Read-onlyIdempotent

Limits, media rules and the settings schema of one channel.

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": {
      "channelId": "<channelId>"
    },
    "name": "mynahcast_get_channel_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYes

Output Schema

NameRequiredDescriptionDefault
mediaYes
channelYes
threadsYes
maxCharsYes
availableYes
firstCommentYes
optionsSchemaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / channel / properties / provider / enum
      Previous value: -[
      -  "bluesky",
      -  "mastodon",
      -  "telegram",
      -  "discord",
      -  "x",
      -  "linkedin",
      -  "youtube",
      -  "tumblr",
      -  "nostr",
      -  "lemmy",
      -  "misskey",
      -  "slack",
      -  "matrix",
      -  "devto",
      -  "hashnode",
      -  "wordpress",
      -  "listmonk"
      -]New value: +[
      +  "bluesky",
      +  "mastodon",
      +  "telegram",
      +  "discord",
      +  "x",
      +  "linkedin",
      +  "youtube",
      +  "tumblr",
      +  "nostr",
      +  "lemmy",
      +  "misskey",
      +  "slack",
      +  "matrix",
      +  "devto",
      +  "hashnode",
      +  "wordpress",
      +  "listmonk",
      +  "instagram",
      +  "threads",
      +  "facebook"
      +]
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the payload contains limits, media rules, and a settings schema, which is useful content-level context, but says nothing about error behavior for invalid or unknown channel IDs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is extremely short with no wasted words, but it is a noun fragment without a leading verb, so it reads as a label rather than a statement of action. Brevity here borders on under-specification rather than efficiency.

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?

An output schema exists, so return-value structure need not be explained, and annotations cover the safety profile for a one-parameter read. Still, for a tool whose whole purpose is discovery of channel limits and rules before publishing, the lack of any usage framing leaves a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain the single parameter, yet it never mentions channelId or that only one channel's capabilities are returned for a UUID. 'One channel' is the only implicit hint; format and scope constraints remain undocumented in prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Limits, media rules and the settings schema of one channel' names the resource content but omits a verb and never says it retrieves them; the tool name carries most of the meaning. It is distinguishable from siblings like mynahcast_list_channels or mynahcast_get_account only by inference, not by explicit contrast.

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 statement of when to call this versus alternatives such as mynahcast_list_channels or mynahcast_get_account, and no prerequisites. The agent must guess that this is the per-channel metadata lookup.

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