Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Zoom Provider

get_report_zoom_provider
Read-onlyIdempotent

Retrieves Zoom call detail for a given month from the IPEX reports API, returning provider-level call data for reporting and analysis.

Instructions

Zoom call detail (provider). IPEX API: GET /v1/reports/zoom/provider/{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": {
      "month": "<month>"
    },
    "name": "get_report_zoom_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesPath parameter 'month' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds only the HTTP verb and route; it says nothing about return content, response size, aggregation granularity, rate limits, or whether historical months are available, so it contributes almost no behavior beyond the annotations.

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 compact sentences with zero filler, and the resource identity is front-loaded before the endpoint mapping. It is arguably too terse rather than padded, so the brevity is not a structural flaw but leaves little for the agent to work with.

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 reporting tool with no output schema, the description should convey what the report returns and the expected month format; neither is present. An agent knows the route but not what it will receive or how to format the required parameter, which are meaningful gaps for a one-parameter report call.

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 'month' path parameter, so the schema does the documenting and baseline 3 applies. The description adds no format hint (e.g. YYYY-MM) or range/validity constraint for 'month' beyond confirming it is a path segment of the IPEX route.

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 data scoped to 'provider' and maps it to a concrete API route (GET /v1/reports/zoom/provider/{month}), which is more than a bare restatement of the name. However, it never explains what 'provider' data contains or how it differs from the sibling get_report_zoom_customer, leaving the distinction to inference from the phrase '(provider)'.

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 at all: no statement of which reporting question this answers, no mention of when to prefer it over get_report_zoom_customer, and no prerequisites. The only selection signal is the implied 'provider' scope in the title-like first fragment.

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