Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Customers

get_report_customers
Read-onlyIdempotent

Fetches the IPEX customer count report to help you track customer base size and support reporting needs.

Instructions

Customer count. IPEX API: GET /v1/reports/customers.

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_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only the HTTP endpoint mapping and nothing about scope, aggregation window, or what the returned count represents, which is the real unknown for a zero-argument report call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two terse fragments with zero waste and the key term front-loaded, which is good for scanning. The trade-off is that the brevity crosses into under-specification; the endpoint line helps engineers but tells an agent little it can act on.

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 parameters and no output schema, the description is the only place to explain what the call returns and under what scope. It never says whether the result is a single integer, a breakdown, or time-bound, leaving an agent unable to judge whether this is the right count tool among its many similar siblings.

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 no parameters and the schema explicitly forbids additional properties, so there is no parameter semantics for the description to explain. Baseline for a zero-parameter tool applies.

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 gives a concrete metric ('Customer count') plus the backing endpoint (GET /v1/reports/customers), so the general idea is clear. But it does not say whose customers are counted, over what scope or period, or how it differs from the many similar sibling report tools. The purpose is identifiable but vague in a crowded namespace.

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 condition that selects this over get_report_provider_customers_count, get_report_top_customers, or plain list_customers, and no prerequisites or exclusions. The endpoint path implicitly frames it as a report call, which is minimal.

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