Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Zoom Customer

get_report_zoom_customer
Read-onlyIdempotent

Retrieves Zoom call details for a specific customer and month, so you can review customer call activity in IPEX reports.

Instructions

Zoom call detail (customer). IPEX API: GET /v1/reports/zoom/customer/{customerId}/{month}.

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": {
      "customerId": "<customerId>",
      "month": "<month>"
    },
    "name": "get_report_zoom_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesPath parameter 'month' of the IPEX API.
customerIdYesPath parameter 'customerId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds only the upstream endpoint (GET /v1/reports/zoom/customer/{customerId}/{month}), which restates the path structure already visible in the schema, and says nothing about the scope of data returned, aggregation, permissions, or empty-result behavior for something backed by an external API.

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?

Two short sentences, no filler, with the core identification front-loaded before the endpoint reference. Nothing is wasted, though the second sentence contributes little beyond what structured fields already convey.

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?

For a simple two-parameter read-only report tool with no output schema and rich annotations, the minimum is met: an agent knows it fetches customer-level Zoom call data for a given month. It still lacks the shape of the returned data and the expected month format, which matter for a reporting endpoint with no output schema.

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%, so both parameters are documented, albeit minimally as "Path parameter 'month'/'customerId' of the IPEX API." The description's path template confirms both are path segments and that month sits alongside customerId, but it adds no format hints (e.g., month as YYYY-MM) beyond what the schema declares.

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?

The description identifies the resource as "Zoom call detail (customer)" and the "(customer)" qualifier hints at the provider counterpart, so it is distinguishable in principle. But "call detail" is vague about what entity is returned (a report row? a list of calls?) and the only real disambiguation comes from the raw API path rather than plain language.

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 guidance on when to use this tool, no prerequisites, and no mention of when to prefer get_report_zoom_provider or other customer report tools. The API path implicitly suggests it needs a customer ID and a month, but that is already in the schema, not added guidance.

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