Skip to main content
Glama

webex_health_check

Validate Webex connectivity and diagnose bot token and room access permissions before starting automated workflows.

Instructions

Validate Webex connectivity and return a structured diagnostic status.

Checks the bot token (identity + API reachability) and, optionally, lists visible rooms to confirm room-access permissions. Designed for agents that need to self-diagnose before starting a workflow.

Args: include_rooms: When True (default), also verify room-list access.

Returns: Standardized success response whose data contains: - overall_status: "healthy", "degraded", or "unhealthy" - checks: per-check result dicts keyed by check name - duration_ms: total wall-clock time for all checks - server_version: running MCP server version - python_version: Python interpreter version string

``overall_status`` is "healthy" when all checks pass, "unhealthy" when
the token check fails, and "degraded" when the token is valid but a
secondary check (e.g. rooms) errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_roomsNo
Behavior5/5

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

No annotations, but description thoroughly explains checks (token, API, optional rooms) and return status conditions (healthy, degraded, unhealthy).

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?

Well-structured with Args and Returns sections. Every sentence adds value; no redundancy.

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?

No output schema, but return structure is fully described. All relevant info is present for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter `include_rooms` explained with default behavior. Schema has 0% coverage; description fully compensates.

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?

Clearly states it validates Webex connectivity and returns structured diagnostic status. Distinct from sibling tools like list_webex_rooms or send_webex_message.

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?

Explicitly says it's for agents that need to self-diagnose workflow preconditions. Doesn't directly state when not to use, but context makes it clear.

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/WebexCommunity/webex-bot-mcp'

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