oitvoip-mcp-server

Official

by OITApps

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

get_user_answer_rules

Retrieve answer rules configured for a user in a VoIP domain to understand call handling behavior.

Instructions

Get answer rules for a user

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

Input Schema

Name	Required	Description	Default
`userId`	Yes	User ID
`domain`	Yes	Domain name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. It only states the action as 'Get', implying read-only, but does not mention permissions, rate limits, error cases, or side effects. The description is insufficient for safe usage.

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 sentence, which is very concise and front-loaded. However, it is arguably too brief, omitting important details. Still, it earns a 4 for efficiency, as every word is functional.

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?

Given the absence of an output schema and the existence of a sibling tool 'get_user_answer_rule', the description should clarify that this tool returns multiple rules. It fails to do so. Also, no examples or constraints are provided for the two required parameters. The description is incomplete for the task complexity.

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% with basic descriptions for 'userId' and 'domain'. The tool description does not add any additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate as no extra value is added.

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

Purpose4/5

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

The description 'Get answer rules for a user' clearly states the action (get) and resource (answer rules for a user). However, it does not differentiate from the sibling tool 'get_user_answer_rule' (singular), which likely retrieves a single rule. The plural suggests multiple rules, but this is not explicitly stated.

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 is provided on when to use this tool versus alternatives. The sibling list includes many get_* tools, but there is no mention of exclusions or specific context. The description does not help the agent decide between this and similar tools.

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