Skip to main content
Glama
OpenSIPS

OpenSIPS MCP Server

Official
by OpenSIPS

fraud_update_rule

Update an existing fraud detection rule by modifying its profile, prefix, time constraints, and threshold values for warnings and critical alerts on call metrics.

Instructions

Update an existing fraud detection rule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ruleidYes
profileidNo
prefixNo
start_hourNo
end_hourNo
daysofweekNo
cpm_warningNo
cpm_criticalNo
call_duration_warningNo
call_duration_criticalNo
total_calls_warningNo
total_calls_criticalNo
concurrent_calls_warningNo
concurrent_calls_criticalNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations exist, so the description must disclose behavioral traits. It fails to mention whether updates are partial or full, whether the rule must exist, if changes take effect immediately, or any side effects.

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?

The description is extremely concise (one sentence) but lacks structure. It earns its place but does not address the tool's complexity, making it insufficiently informative.

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

Completeness1/5

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

With 14 parameters and no output schema description, the description is wholly incomplete. The agent has no guidance on parameter interplay, return values, or usage patterns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to the 14 parameters. The agent must rely solely on schema titles, which lack context for usage.

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 'Update an existing fraud detection rule' clearly states the verb (update) and the resource (fraud detection rule), distinguishing it from sibling tools like fraud_add_rule and fraud_delete_rule.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 (e.g., fraud_add_rule vs fraud_update_rule), nor are prerequisites or when-not-to-use scenarios mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OpenSIPS/opensips-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server