Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_search_spaces

Search Webex spaces by case-insensitive title substring and filter by space type, team, or activity order to locate relevant group or direct spaces.

Instructions

Find spaces by case-insensitive title substring.

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": {
      "query": "<query>"
    },
    "name": "webex_search_spaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoSpace type
queryYesTitle substring
sortByNoAPI scan order (default: lastactivity)
teamIdNoTeam ID filter
scanLimitNo
maxResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that matching is case-insensitive and substring-based, but it does not explain pagination, scan limits, result ordering, or what the search returns.

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 definition is a single front-loaded sentence with no wasted wording. The core matching behavior is stated immediately.

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 six-parameter search tool with no annotations and no output schema, this one-sentence description is under-specified. It omits usage guidance and key behavioral details such as how scanLimit, maxResults, and sortBy affect results.

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 67%, and the schema documents several parameters. The description adds only the case-insensitive nuance for 'query' and does not clarify teamId, type, sortBy, scanLimit, or maxResults beyond the schema.

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 states a specific verb and resource, 'Find spaces', plus the matching condition 'by case-insensitive title substring'. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as webex_list_spaces or webex_get_space.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The substring-search phrasing implies when to use it: when looking for spaces by partial title. However, it gives no explicit alternatives, no when-not guidance, and no mention of when to use webex_list_spaces or webex_get_space instead.

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