Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_get_person

Retrieve a Cisco Webex person's profile by ID, or use "me" to fetch the current user's details. Use it to resolve user identities and access contact information.

Instructions

Get person by ID; "me" selects current user.

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": {
      "id": "<id>"
    },
    "name": "webex_get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPerson ID or "me"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full behavioral burden. It discloses only the 'me' shortcut and says nothing about permission requirements, what happens with an invalid or inaccessible ID, or what person fields are returned.

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 compact sentence with the core action front-loaded and no filler. Brevity here costs little, though the description is thin enough that it reads more like a label than an explanation.

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 tool is simple (one required parameter) but has no output schema, so an agent gets no indication of what a 'person' object contains. The description is adequate to invoke the tool but not to anticipate its result.

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% and the schema already documents the single parameter as 'Person ID or "me"'. The description restates the 'me' behavior without adding format details or ID-source guidance, so baseline 3 applies.

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 pairs a specific verb with a specific resource ('Get person by ID'), which clearly separates it from the sibling list tool webex_get_people. It does not name that sibling explicitly, but the 'by ID' qualifier makes the distinction inferable.

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?

Usage is implied by the 'by ID' phrasing: call this when you already have an identifier. There is no explicit guidance about when to prefer webex_get_people for lookup/search, and no mention of error behavior for an unknown ID.

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