Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Customer Requests Count

get_report_customer_requests_count
Read-onlyIdempotent

Retrieves the order request count for a specific customer using the IPEX report API. Use it to check how many requests a customer has placed.

Instructions

Order count of a customer. IPEX API: GET /v1/reports/customers/{customerId}/requests/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_requests_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYesPath parameter 'customerId' 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, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered elsewhere. The description adds only the upstream IPEX endpoint path; it says nothing about what is counted, over what time window, whether results are cached or real-time, or 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 no filler, and the metric statement is front-loaded before the API reference. Slightly fragmentary rather than a coherent sentence, but nothing is wasted.

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?

There is no output schema, so the description must convey what comes back, and it does not — a bare number versus an object with a count field is unspecified. The order-versus-request ambiguity and the missing time scope are material gaps for a reporting/count tool an agent will cite in answers.

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?

With a single parameter at 100% schema description coverage, the schema already documents customerId fully. The description contributes no additional semantics such as accepted ID formats or where to obtain a customerId (e.g., get_customer).

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?

"Order count of a customer" names a resource and a metric, but it conflicts with the tool name's "requests count" and the API path's "/requests/count", leaving ambiguous whether it counts orders or requests. There is no differentiation from siblings like get_report_provider_requests_count or get_report_customer_services_count beyond the customer-vs-provider scope being implicit.

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 guidance on when to use this instead of the provider variant, the services count, or the generic list_requests tool. The only implied usage is the customer scope, which the agent must infer from the parameter 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