Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Channel Refresh

channel_refresh

Fetches new messages from a channel immediately, so you can get updates without waiting for the next scheduled retrieval.

Instructions

Fetch new messages from a channel now instead of waiting for the next scheduled retrieval.

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

Input Schema

NameRequiredDescriptionDefault
channelIdYesThe channel id (see channel_list).
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.5/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, meaning this triggers a side-effecting, non-idempotent job, yet the description's 'Fetch' wording reads like a harmless read. Nothing tells the agent about rate limits, per-channel cost, throttling, whether repeated calls duplicate work, or what a successful response contains. This is the main weakness of the definition.

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?

One sentence, front-loaded with the action and immediately followed by the reason to choose it. No filler, no restatement of the title.

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?

For a simple two-parameter tool with full schema coverage and no output schema, the description covers what the tool does and why you would pick it. It is still incomplete on the consequences of a non-idempotent, non-read-only call, which is the one thing an agent could get wrong here.

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%: channelId points to channel_list and organizationId to organization_list, so both parameters are already fully documented in structured data. The description adds no additional meaning about identifiers or formats, which is the correct baseline for a fully-described two-parameter schema.

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 ('Fetch new messages from a channel') plus a timing qualifier ('now'), which is enough for an agent to distinguish this from an ordinary read. It does not name any sibling tool, so differentiation relies on the scheduled-retrieval contrast rather than an explicit alternative.

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 phrase 'instead of waiting for the next scheduled retrieval' gives a clear trigger condition: use this when freshness is required and the next scheduled poll is too late. It stops short of stating when NOT to call it (e.g. shortly after a scheduled run, or in tight loops), so the guidance is clear but not complete.

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

Deploy Server

Other Tools