Skip to main content
Glama
Sign In
Vicarius vRx MCP Server

Vicarius vRx MCP Server

by Space-C0wboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

endpoint_delete_many

Disable multiple endpoint instances using a query parameter and JSON request body.

Instructions

endpoint · DELETE /endpoint/deleteMany — Disable instance of the objects. Required: q. Requires a JSON request body.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "endpoint_delete_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoquery param q (str)
bodyNoJSON request body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.2/5.0
Behavior1/5

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

The description contradicts the schema by stating 'Required: q' while the schema marks q as optional with a default of null. No annotations are provided. The term 'Disable instance' is ambiguous and does not clarify if the action is destructive or reversible.

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 short but includes redundant elements like 'endpoint ·' and repeats information from the schema. It is not efficiently structured for clarity.

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 no annotations or output schema, the description lacks critical details: what 'q' represents, how to specify which instances to delete, the response format, and whether 'disable' means soft or hard delete.

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 already describes both parameters (q as a string query param, body as JSON). The description adds 'Required: q' which is misleading. No additional meaning is provided beyond the schema, and the contradiction reduces reliability.

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

Purpose3/5

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

The description states the HTTP method and path, and vaguely indicates disabling instances, but does not clearly say it deletes multiple endpoints. It also fails to differentiate from the sibling 'endpoint_delete' tool.

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 on when to use this tool versus alternatives. The description mentions 'Required: q' but does not explain what q is or provide context for appropriate usage.

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

Deploy Server

Other Tools