Skip to main content
Glama

Pause Bot

neuron_pause_bot

Pause a bot's operations to stop responding to messages temporarily. Resume later to continue interactions.

Instructions

Pause a bot's operations temporarily. The bot will stop responding to messages until resumed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the bot to pause
Behavior3/5

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

The description discloses that the bot stops responding to messages and that the pause is temporary until resumed. However, it does not discuss potential side effects like whether pending operations are cancelled or if any data is affected. Given the lack of annotations, the description provides basic but incomplete transparency.

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?

The description is very concise, using two short sentences. Every word contributes to the meaning, but it could be slightly more informative without sacrificing conciseness.

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?

The description covers the core effect (stop responding until resumed) but lacks context about reversibility, impact on other bot operations, or expected response. Given no output schema and no annotations, additional context would be beneficial.

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?

The input schema has 100% coverage with a description for the 'id' parameter. The description adds no additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 clearly states the tool pauses a bot and specifies the effect (stops responding to messages). It is specific about the resource (bot) and the action (pause), but does not explicitly differentiate from the sibling tool neuron_pause_campaign, though the bot vs campaign distinction is implied.

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?

No guidance is provided on when to use this tool versus alternatives like neuron_resume_bot or neuron_pause_campaign. There is no mention of prerequisites, contexts, or when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conquext/neuron-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server