Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Ctu

get_report_ctu
Read-onlyIdempotent

Retrieves Czech Telecommunications Office (ČTÚ) statistics reports from the IPEX API, filtered by report type, statistics type, and date range.

Instructions

ČTÚ statistics. IPEX API: GET /v1/reports/cz/ctu.

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

Input Schema

NameRequiredDescriptionDefault
byTypeNoQuery parameter 'byType' of the IPEX API.
dateToNoQuery parameter 'dateTo' of the IPEX API.
dateFromNoQuery parameter 'dateFrom' of the IPEX API.
statsTypeNoQuery parameter 'statsType' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no repetition. The description adds only the upstream API path; it says nothing about pagination, rate limits, auth requirements, or what the returned statistics look like.

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 very short sentences with no wasted words and the resource identified first. However, the terseness crosses into under-specification – brevity here comes at the cost of the information an agent actually needs.

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 four-parameter statistical reporting tool with no output schema and opaque parameter names (byType, statsType), the description should explain at least what the report returns and what the filter values mean. As written, an agent can only guess at correct invocation.

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 four query parameters are formally documented, though only tautologically ('Query parameter X of the IPEX API'). The description adds no meaning about valid values for byType/statsType or accepted date formats, so it neither helps nor hurts beyond the baseline.

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 names a resource ('ČTÚ statistics') and an underlying endpoint (GET /v1/reports/cz/ctu), which hints at a statistical report fetch. But it never states what the statistics cover (call volumes, number portability, etc.), so an agent cannot confidently distinguish it from the many get_report_* siblings.

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 guidance on when to use this tool versus the numerous sibling report tools (get_report_numbers, get_report_customers, get_report_top_customers, etc.). The only implicit cue is 'ČTÚ statistics', which assumes the agent already knows what ČTÚ data is and when it is relevant.

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