Skip to main content
Glama
Sign In
Vicarius vRx MCP Server

Vicarius vRx MCP Server

by Space-C0wboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

organization_endpoint_group_update

Update an organization endpoint group by submitting a JSON request body to modify its configuration.

Instructions

organization_endpoint_group · POST /organizationEndpointGroup/update — Update instance of the object 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": "organization_endpoint_group_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON request body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must cover behavioral traits. It only states 'Update instance' and 'Requires a JSON request body', omitting idempotency, error handling, side effects, or required permissions.

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 (one sentence) but includes redundant info like the tool name and path. It could be more structured and omit the prefix.

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?

For an update tool with no output schema and one parameter, the description lacks crucial details such as required body fields, expected object IDs, and response behavior. It is incomplete for reliable agent usage.

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 coverage is 100% for the single 'body' parameter. The description repeats 'JSON request body' from the schema, adding no additional meaning about expected fields or structure.

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 clearly states 'Update instance of the object' with the HTTP method and path, distinguishing it from sibling tools like delete or insert. However, it lacks specifics on what fields can be updated, which slightly reduces clarity.

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 (e.g., organization_endpoint_group_insert). No prerequisites, conditions, or examples are mentioned.

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