Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Calls

get_calls
Read-onlyIdempotent

Retrieves a list of IPEX calls filtered by date range and optional parameters, such as phone number or customer ID.

Instructions

Call listing (výpis hovorů). IPEX API: GET /v1/calls.

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": {
      "dateFrom": "<dateFrom>"
    },
    "name": "get_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateToNoQuery parameter 'dateTo' of the IPEX API.
numberNoQuery parameter 'number' of the IPEX API.
showUIDNoQuery parameter 'showUID' of the IPEX API.
showVATNoQuery parameter 'showVAT' of the IPEX API.
dateFromYesQuery parameter 'dateFrom' of the IPEX API (required).
externIdNoQuery parameter 'externId' of the IPEX API.
showUnitNoQuery parameter 'showUnit' of the IPEX API.
showFlagsNoQuery parameter 'showFlags' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
typHistoryNoQuery parameter 'typHistory' of the IPEX API.
showCDRTypeNoQuery parameter 'showCDRType' of the IPEX API.
showFreeUnitsNoQuery parameter 'showFreeUnits' of the IPEX API.
showCustomerIdNoQuery parameter 'showCustomerId' 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 covered. The description adds nothing beyond that — no pagination behavior, no result limits, no rate-limit or auth notes, and no indication of how large a date range is safe to request against the external IPEX API.

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?

The description is a single front-loaded line with zero filler, which is structurally clean. Its brevity is not the problem; the problem is what is omitted, which is scored under other dimensions.

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?

For a 13-parameter listing tool with no output schema, the description is far too thin: it explains neither the returned call-record shape nor the semantics of the many optional filter/toggle parameters. An agent can identify the tool but cannot confidently construct a correct call.

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 nominally 100%, which sets the baseline at 3. But those schema descriptions are pure boilerplate ('Query parameter X of the IPEX API'), so the description provides no compensating meaning for the 13 parameters — nothing about date format, what showUID/showVAT/showFlags toggles actually control, or how typHistory and customerId narrow the listing.

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 says it is a call listing and names the underlying endpoint (GET /v1/calls), so an agent knows it retrieves call records. However, 'Call listing' largely restates the title 'Get Calls' and adds no scope information (all calls vs. filtered, single customer vs. provider-wide), and it does not distinguish it from the sibling get_calls_technical_overview.

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 prerequisites, no indication of what the required dateFrom window means, and no mention of when to prefer this over get_calls_technical_overview or other reporting siblings. The agent must infer usage entirely from the tool name.

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