AccountHub

schedule_message

Destructive

Schedule a Slack message to post later (chat.scheduleMessage). to is a channel ('#name' or id), user id, or 'me' (DM to self); post_at is a Unix timestamp in SECONDS, at least 60s in the future. Pass account when more than one Slack workspace is connected (see list_accounts). Needs chat:write (granted since the first Slack connect — no reconnect). Posting to a PUBLIC channel the bot hasn't joined additionally needs chat:write.public (reconnect if the workspace predates it); a PRIVATE channel always needs the bot invited (/invite) regardless. This actually schedules delivery — confirm the target, text, and time with the user before calling.

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": {
      "to": "<to>",
      "text": "<text>",
      "post_at": "<post_at>"
    },
    "name": "schedule_message"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Channel ('#name' or id), user id, or 'me' (DM to self).
`text`	Yes	Message text.
`account`	No	Workspace label (see list_accounts). Required when several workspaces are connected.
`post_at`	Yes	When to post — Unix timestamp in SECONDS, at least 60s in the future.
`thread_ts`	No	Reply into this thread (ts of the parent message).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes well beyond the destructiveHint annotation by disclosing that the call actually schedules delivery, describes the required OAuth scopes, explains public-vs-private channel invite requirements, and instructs the agent to confirm target, text, and time before calling. These are exactly the behavioral details an agent needs for a mutation tool.

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?

The description is front-loaded with the core purpose, then layers in parameter syntax, workspace selection, permissions, and a pre-call confirmation rule. Every sentence earns its place despite the length, and there is no filler.

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?

For a scheduling tool with no output schema and only sparse annotations, the description covers the necessary call semantics, prerequisites, channel constraints, and a safety confirmation. Nothing essential to correct invocation 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%, so all five parameters are already documented in the schema. The description mostly repeats those parameter meanings, adding only the useful pointer to list_accounts for the account parameter; the baseline of 3 is appropriate when structured fields already carry the semantic load.

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

Purpose5/5

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

The description states a specific verb and resource: 'Schedule a Slack message to post later', and pairs it with the underlying API method. The future-delivery framing clearly distinguishes it from send_message and other Slack messaging siblings without needing to name them.

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 when to use the tool (posting later) and states important prerequisites for account selection and channel permissions. It stops short of explicitly naming alternatives such as send_message or cancel_scheduled_message, so it does not reach the top usage-guidance tier.

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

All AccountHub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?