Skip to main content
Glama

Is the bot alive in a channel

dosai_get_channel_activity
Read-onlyIdempotent

For one channel: when the bot last answered a client there (null = not once in the recent chats) and how many client conversations the channel has. A quick answer to "is the bot working in Instagram".

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": {
      "project_id": "<project_id>",
      "channel": "<channel>"
    },
    "name": "dosai_get_channel_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.6/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 closed-world scope, so the safety profile is covered. The description adds one genuinely useful disclosure — null means the bot never answered in the recent chats, and the count is scoped to 'recent chats' — but it doesn't clarify how far back 'recent' reaches or the timestamp format, and offers no return shape details.

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?

Front-loaded with 'For one channel:' and free of filler; the null-semantics parenthetical and the quoted example both earn their place. Phrasing is slightly convoluted ('when the bot last answered a client there'), but nothing is redundant.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the description covers purpose, both returned values in prose, and the null caveat — enough to invoke and interpret it correctly. The remaining gaps (time window of 'recent', exact field names/format) are minor but real given there is no output schema to fall back on.

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?

With 50% schema coverage, project_id is documented ('From dosai_list_projects') while the channel enum values are not described beyond the passing 'Instagram' example. The description conveys that channel scopes the whole query to one channel, but adds no guidance on the enum members or on choosing a project.

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?

The description names a specific resource (one channel's bot activity) and the two facts returned: the last time the bot answered a client there and the number of client conversations in that channel. The closing 'is the bot working in Instagram' makes the intent unmistakable, though it doesn't explicitly contrast with siblings like dosai_get_analytics or dosai_get_bot_settings.

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?

It gives clear context for use — a quick liveness/diagnostic check per channel ('is the bot working in Instagram'), which tells the agent when this is the right lightweight tool. It stops short of naming alternatives or stating when not to use it (e.g. for deeper conversation analytics).

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