Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Numbers

get_report_numbers
Read-onlyIdempotent

Retrieve service count reports for IPEX numbers, with optional filters for status, customer, number type, and payment type, to review number inventory and reporting data.

Instructions

Service count. IPEX API: GET /v1/reports/numbers.

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

Input Schema

NameRequiredDescriptionDefault
showNoQuery parameter 'show' of the IPEX API.
statusNoQuery parameter 'status' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
numberTypeNoQuery parameter 'numberType' of the IPEX API.
paymentTypeNoQuery parameter 'paymentType' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/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 safety is covered. The description adds no behavior beyond that: it does not say whether the result is a scalar count or a collection, whether results are paginated, or how the API behaves with no filters applied.

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 no padding, so nothing is wasted, but the front-loaded phrase is the vaguest part of the definition and the endpoint string consumes half the available text without adding decision value.

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?

A five-parameter, no-required-parameter reporting tool with no output schema needs the description to explain what the filters do and what shape the result takes; the definition does neither, so an agent cannot confidently invoke it or interpret its return value.

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 coverage is 100%, so all five query parameters are documented at the structured level, which sets the baseline at 3. However, the schema descriptions are tautological ("Query parameter 'show' of the IPEX API"), and the tool description does not clarify what show, status, numberType or paymentType actually filter, leaving the 100% coverage largely uninformative.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Service count" gestures at a counting operation but never says what is counted or in what unit, and it is indistinguishable from siblings such as get_report_customer_services_count or get_report_connector_phone_numbers_count. The REST endpoint path is the only concrete detail, and it describes implementation rather than purpose.

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?

No when-to-use guidance, no alternatives, no exclusions, no prerequisites. The definition offers nothing to help an agent decide between this and the other get_report_* count tools beyond the raw endpoint URL.

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