Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Calls Technical Overview

get_calls_technical_overview
Read-onlyIdempotent

Retrieve a VoIP technical overview of calls using IPEX API data, with optional filters for number and date range to inspect call quality and connection details.

Instructions

VoIP technical overview. IPEX API: GET /v1/calls/technical-overview.

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

Input Schema

NameRequiredDescriptionDefault
dateToNoQuery parameter 'dateTo' of the IPEX API.
numberNoQuery parameter 'number' of the IPEX API.
dateFromNoQuery parameter 'dateFrom' 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 readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds nothing beyond the HTTP path — not whether a date range is required for sensible results, not the aggregation granularity, not rate or volume characteristics.

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 short fragments with no wasted wording, but the brevity comes at the cost of under-specification rather than economy — the sentence that would explain the payload is simply absent.

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 is the only place a caller could learn what a "technical overview" returns, and it does not. For a reporting-style read tool with three filtering parameters, the agent has insufficient basis to interpret 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 three parameters (dateFrom, dateTo, number) are documented in the schema itself; baseline 3 applies. The description adds no extra meaning such as expected date format or how number filtering interacts with the date range.

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?

"VoIP technical overview" essentially restates the tool name and leaves the resource/action ambiguous — it never says what data is returned (codec stats? MOS scores? call quality metrics?). The API endpoint reference is implementation detail rather than a statement of purpose, and nothing distinguishes it from sibling get_calls.

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 versus get_calls or the many report_* siblings, no prerequisites, no exclusions. The agent must guess from the name alone.

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