Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_get_membership

Retrieves a Webex space membership by membership ID so you can inspect or verify a member's access and role.

Instructions

Get space membership 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": {
      "membershipId": "<membershipId>"
    },
    "name": "webex_get_membership"
  }
}

Input Schema

NameRequiredDescriptionDefault
membershipIdYesMembership ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and provides almost nothing: it does not say whether the caller needs to be a member of the space, what happens for a nonexistent or inaccessible ID, or what fields the response contains. For a read tool in a permissions-gated API like Webex, this is a meaningful gap.

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 short sentence with no filler and the key scoping qualifier ("space") front-loaded. It is efficient, though arguably efficient to the point of under-specification.

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?

No output schema and no annotations mean the description is the only source of behavioral information, and it says nothing about the returned membership object, error cases, or where the ID comes from. For a lookup tool an agent must chain after a list call, that context 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?

Only one parameter exists and schema coverage is 100%, so the schema already documents membershipId fully. The phrase "by ID" adds nothing beyond that baseline, which is acceptable given the schema does the work.

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?

States a specific verb and resource ("Get space membership") scoped by ID, which contrasts reasonably with the list/create/update/remove membership siblings. It does not explicitly distinguish itself from webex_get_team_membership, but the "space" qualifier implicitly separates them.

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 on when to use this versus webex_list_memberships or webex_get_team_membership, and no mention of prerequisites such as needing the membership ID from a prior list call. 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