calltouch-mcp

get_statistics

Retrieve daily call statistics including total, unique, targeted, and missed calls. Filter by date range and group by day, week, or month.

Instructions

Статистика звонков по дням: всего, уникальных, целевых, пропущенных.

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": {
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "get_statistics"
  }
}

Input Schema

Name	Required	Description
`date_from`	Yes	Дата начала в формате dd/MM/yyyy
`date_to`	Yes	Дата окончания в формате dd/MM/yyyy
`group_by`	No	Группировка: day, week, month (по умолчанию day)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0May 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations are absent, so description must cover behavioral traits. It does not disclose data freshness, aggregation method, timezone handling, or any limits. For a statistics tool, these are critical gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence that conveys the tool's purpose without unnecessary words. No filler or redundancy.

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?

Despite low complexity (3 parameters, no output schema), the description omits important details about the return format or structure of the statistics, which is essential for an agent using this tool.

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 covers all three parameters with descriptions (100% coverage). Description adds no extra parameter information beyond what is in the schema, so baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it provides call statistics by day with breakdowns (total, unique, targeted, missed). It uses a specific verb and resource, and distinguishes from sibling tools like get_calls which likely return individual call records.

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 tool versus alternatives like get_calls or other statistics tools. Does not specify prerequisites or scenarios where this tool is preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server