Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Customer Services Count

get_report_customer_services_count
Read-onlyIdempotent

Retrieves the number of services for a specified customer, with an optional service type filter, using the IPEX customer services count report.

Instructions

Service count of a customer. IPEX API: GET /v1/reports/customers/{customerId}/services/count.

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>"
    },
    "name": "get_report_customer_services_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoQuery parameter 'type' 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.9/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 upstream API endpoint, which is provenance rather than behavior — nothing about what 'counts as a service', whether the count includes shared or inactive services, or freshness of the report.

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, front-loaded sentences with no filler. The endpoint clause is somewhat redundant with the tool's purpose but useful for tracing to the underlying API; nothing is padded.

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?

This is a simple read-only report with one required path parameter and full schema coverage, so an agent can invoke it correctly from what exists. However, the opaque 'type' filter and the absence of any note on what the count represents (scope, availability of services) leave gaps for correct interpretation of results.

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 the baseline is 3. The description confirms customerId is the path parameter via the endpoint template but adds no meaning for the 'type' query parameter, whose schema text is circular ('Query parameter type of the IPEX API'), leaving its allowed values and filtering effect unexplained.

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 names a specific resource and measurement: 'Service count of a customer.' Combined with the endpoint path, an agent can tell this is a counting report scoped to a single customer, which distinguishes it from siblings like get_report_customer_requests_count. It stops short of a strong verb-and-scope formulation, but the purpose is unambiguous.

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 versus the many sibling reports (requests count, invoices sum, list_services), nor any prerequisites or exclusions. The agent must infer appropriate use entirely from the name and endpoint.

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