Skip to main content
Glama

Send a new confirmation code

resend_channel_code
Destructive

Send a new code to a channel that is waiting for one. Earlier codes stop working. Up to 8 codes an hour per account.

Permission: channels:manage.

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

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, and the description goes further with information annotations cannot express: previously issued codes are invalidated, a rate limit of 8 codes per hour per account, and the required channels:manage scope. That is exactly the extra context an agent needs before triggering a mutation.

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?

Three short sentences, each earning its place: the action, the side effect, the rate limit, and the permission. The invalidation warning and quota are front-loaded rather than buried.

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

Completeness5/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 values need not be described, and for a single-parameter mutation the description covers the safety-relevant behavior (invalidation, quota, scope) that an agent must know. Nothing material is missing.

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% for the single channel_id parameter, so the schema already carries the semantics; the description adds nothing about the parameter itself. Baseline 3 applies when structured data does the work.

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 — 'send a new code' to 'a channel that is waiting for one' — which distinguishes it from confirm_channel (verifying a code) and add_channel by implication. It stops short of naming the sibling it is not, so it is clear but not maximally differentiated.

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?

The precondition 'a channel that is waiting for one' gives an agent a concrete condition for selecting this tool, and the note that earlier codes stop working implies the resend case. It does not explicitly exclude alternatives (e.g., directing an agent to confirm_channel when a code already exists), so the routing guidance is context-bearing but not exhaustive.

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