Vilix AI

delete_skill

DestructiveIdempotent

Destructive — deletes a skill. Only call when the user explicitly asks to delete or remove a skill.

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": {
      "skill_id": "<skill_id>"
    },
    "name": "delete_skill"
  }
}

Input Schema

Name	Required	Description	Default
`skill_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

Behavior3/5

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

Annotations already declare destructiveHint and idempotentHint, so the description's leading 'Destructive' is redundant. It adds a useful user-consent condition and names the destroyed resource, but does not disclose consequences like irreversibility or related data effects. No contradiction with annotations.

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 key warning front-loaded and zero filler. Every clause adds either action, condition, or guidance.

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 one-parameter destructive tool, the description plus annotations and output schema cover the important cases: what it deletes and when it is permitted. It could mention how to obtain skill_id, but the sibling get_skill/list_skills and the obvious parameter name make this a minor gap.

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?

The schema provides no description for skill_id (0% coverage), and the description does not explain where the ID comes from, its format, or that it must reference an existing skill. The mapping is only implicit through the phrase 'deletes a skill.'

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 clearly identifies the action ('deletes a skill') and the resource, distinguishing it from sibling delete_task/delete_project and update_skill. The verb is specific and the scope is unambiguous.

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

Usage Guidelines5/5

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

Provides an explicit gate: only call when the user explicitly asks to delete or remove a skill. This tells the agent exactly when to invoke the tool and implicitly warns against inferring intent.

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?