Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Provider Requests Count

get_report_provider_requests_count
Read-onlyIdempotent

Retrieves provider order request counts from IPEX reports, with optional filtering by state.

Instructions

Order count (provider). IPEX API: GET /v1/reports/providers/requests/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_requests_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoQuery parameter 'state' 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 readOnly, idempotent, non-destructive and open-world behavior, so the description's only added signal is the endpoint path, which implies a remote read. It says nothing about what the count covers, what time window applies by default, or what happens when state is omitted.

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 padding, and the resource description is front-loaded before the endpoint reference. It is terse rather than verbose, though 'Order count (provider)' is slightly muddled phrasing.

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 should at least confirm the return value is a single count and clarify what 'state' selects in a report context. As written, an agent cannot tell what the number represents or how it differs from the neighboring provider/customer count reports.

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% and the single 'state' parameter is already documented in the schema, so the description adds no meaning beyond it. Baseline 3 applies when the schema carries the full parameter burden.

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 (provider)" plus the endpoint path gives a rough sense that this returns a count of provider-side requests, but the wording conflates 'orders' with 'requests' (the tool name) and never states plainly that it returns a numeric count. It also does nothing to distinguish itself from siblings like get_report_provider_customers_count or get_report_customer_requests_count beyond the endpoint string.

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 indication of when to use this tool versus the many sibling report-count tools, nor any note about prerequisites such as a required date range or provider context. The agent must infer usage entirely from the tool name and the raw endpoint path.

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