Vilix AI

remove_user_rule

DestructiveIdempotent

Destructive — removes a user_rule. Only call when the user explicitly asks to delete or remove a rule.

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": {
      "rule_id": "<rule_id>"
    },
    "name": "remove_user_rule"
  }
}

Input Schema

Name	Required	Description	Default
`rule_id`	Yes

Output Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`message`	No
`upgrade_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark the tool as destructive and not read-only. The description reinforces this and adds an important behavioral guardrail: explicit user consent is required before calling. It does not detail side effects, but the annotations plus this condition provide adequate transparency.

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?

Two short sentences with the destructive warning front-loaded. There is no filler, and every sentence earns its place.

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

Completeness4/5

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

For a simple one-parameter destructive tool with an output schema and rich annotations, the description covers purpose, risk, and invocation conditions well. The only minor gap is guidance on sourcing rule_id, but the surrounding sibling tools like list_user_rules make this a small omission.

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

Parameters2/5

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

Schema description coverage is 0%, and the description says nothing about rule_id beyond the tool name. The agent must infer that rule_id is the identifier of the user_rule and how to obtain it, which is a notable gap for the only required parameter.

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?

The description states the exact operation: 'removes a user_rule'. It clearly distinguishes this from sibling tools like add_user_rule, update_user_rule, and list_user_rules, and the verb is specific and unambiguous.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit invocation condition: 'Only call when the user explicitly asks to delete or remove a rule.' This clearly implies not to call it for other intents, though it does not name alternative tools such as update_user_rule.

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

All Vilix AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?