Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Channel Statistics

channel_statistics
Read-onlyIdempotent

Retrieve conversation volume statistics for each channel within an organization by providing its organization ID.

Instructions

Statistics per channel of an organization (conversation volumes).

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>"
    },
    "name": "channel_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured fields. The description adds that output is conversation-volume statistics per channel, but it does not disclose the return shape, aggregation window, ordering, or whether empty channels appear.

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?

One short sentence with no wasted words, and the scope (per channel, per organization) is front-loaded. It is terse to the point of under-specification rather than padded.

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 single-parameter read tool with full annotations and documented params, the essential information to invoke it correctly is present. It falls short on what the caller will actually receive, which matters because there is no output schema to define the statistics payload.

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?

There is a single parameter (organizationId) at 100% schema description coverage, and the schema itself already instructs the agent to resolve it via organization_list. The description contributes no additional meaning about the identifier, so the schema-driven baseline of 3 applies.

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 resource (channel statistics for an organization) and clarifies the metric measured (conversation volumes), which distinguishes it from performance/agent statistics tools. The only gap is that it is phrased as a noun fragment with no verb, so an agent must infer that it retrieves rather than computes or mutates data.

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?

Provides no explicit when-to-use guidance, no exclusions, and no mention of the closest alternative such as classification_statistics. The implicit routing signal is only the word 'channel', and the loader must infer the rest from the sibling list rather than from the description.

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