Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Provider Customers Count

get_report_provider_customers_count
Read-onlyIdempotent

Retrieve the total customer count for a provider from IPEX reports, enabling a quick overview of provider customer volume.

Instructions

Customer count (provider). IPEX API: GET /v1/reports/providers/customers/count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_report_provider_customers_count"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds essentially nothing beyond restating the endpoint, omitting which provider is counted, whether the count is time-scoped, and what the response looks like.

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 fragments with zero filler, front-loading the returned metric before the API reference. The terseness edges toward under-specification rather than verbosity.

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?

With no output schema, the description carries the burden of explaining the return value, yet it never states that a numeric count is returned, what entity provider refers to (presumably the authenticated account), or whether any filtering applies. For a no-parameter reporting tool this leaves real gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline is 4. Nothing in the description misrepresents the empty input.

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 phrase "Customer count (provider)" identifies the resource (customers) and the returned metric (count), scoped to a provider, and the API path reinforces it. However, the noun-phrase style leaves the verb implicit and does not differentiate it from nearby siblings such as get_report_customers or get_report_top_customers, nor does it clarify what "provider" scope means.

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 count endpoint versus the list-style siblings (get_report_customers) or the other count endpoints (get_report_customer_requests_count, get_report_connector_phone_numbers_count). The agent must infer the selection from names alone.

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