Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_get_space

Fetches a Webex space by its room ID to inspect space details and confirm the correct space before managing messages or memberships.

Instructions

Get space by ID.

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": {
      "roomId": "<roomId>"
    },
    "name": "webex_get_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomIdYesSpace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about permissions, error behavior for an invalid or inaccessible ID, or what a "space" record contains. For a simple read it is not misleading, but it discloses no behavior at all.

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?

A single front-loaded sentence with zero waste or filler. It is efficient, though its brevity borders on under-specification rather than being a model of tight structure.

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

Completeness2/5

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

For a one-parameter lookup with no output schema and no annotations, the description should at least hint at what is returned or what a space represents. As written, an agent knows how to call it but nothing about the result or failure modes.

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% for the single parameter, so the schema already defines roomId as "Space ID"; the phrase "by ID" in the description adds only marginal confirmation that this is a lookup key. Baseline 3 applies since the schema does the documentation work.

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

Purpose3/5

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

"Get space by ID" names a verb and resource and implies single-record retrieval keyed by identifier, which distinguishes it somewhat from the list/search siblings. However, it largely restates the tool name (webex_get_space) with no additional scope or return-content detail, so it is only minimally clarifying.

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?

There is no when-to-use guidance: nothing tells the agent to prefer this over webex_list_spaces or webex_search_spaces when the ID is unknown, nor any prerequisite such as needing a valid space ID. Usage must be inferred entirely from the name.

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