oitvoip-mcp-server

Official

by OITApps

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

get_agent_statistics

Retrieve agent statistics for a domain, optionally filtering by specific agent ID to analyze performance.

Instructions

Get agent statistics for a domain

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": {
      "domain": "<domain>"
    },
    "name": "get_agent_statistics"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name
`agentId`	No	Optional specific agent ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 3, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided; description only states it gets statistics without disclosing behavioral aspects like required permissions, whether it aggregates data, or latency. The agent has no hints about side effects or state changes.

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, directly states the purpose with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple tool with 2 parameters and no output schema; description is minimally complete for a retrieval operation but doesn't clarify what 'statistics' entails, leaving the agent uncertain about return format.

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% with descriptions for 'domain' and 'agentId', so the schema already documents parameters. The description adds 'for a domain' which aligns but doesn't enhance understanding beyond the schema.

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 uses specific verb 'get' and resource 'agent statistics for a domain', clearly distinguishing from siblings like get_agents or get_auto_attendants.

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 explicit guidance on when to use this tool versus alternatives like get_agents or login_agent. The description implies it's for statistics but doesn't state conditions or when not to use it.

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