Skip to main content
Glama
G-Core
by G-Core

cloud_insts_unassign_secgrp

Unassigns a security group from a server. Use NULL port_id to remove groups from all ports.

Instructions

Un-assign the security group to the server.

To un-assign multiple security groups to all ports, use the NULL value for the port_id field

Args: name: Security group name, applies to all ports

ports_security_group_names: Port security groups mapping

extra_headers: Send extra headers

extra_query: Add additional query parameters to the request

extra_body: Add additional JSON properties to the request

timeout: Override the client-level default timeout for this request, in seconds

Note: Pass the numeric project_id. When a project name is provided, resolve it via cloud.projects.list/cloud.projects.get. If nothing is specified, fetch the account's default project first and use that ID. Pass the numeric region_id. Resolve region names with cloud.regions.list or cloud.regions.get. If no region is mentioned, obtain the default region ID before calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYes
project_idYes
region_idYes
nameNo
ports_security_group_namesNo
extra_headersNo
extra_queryNo
extra_bodyNo
timeoutNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool expects numeric IDs and explains how to resolve them via other tools. However, it does not mention authentication, rate limits, side effects, or idempotency.

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 moderately concise but has an unstructured 'Args' list and a long note that could be condensed. The main action sentence is clear, but the extra details could be better organized.

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 the tool has 9 parameters (3 required), no output schema, and no annotations, the description leaves gaps: no description for 'instance_id', vague explanation of 'ports_security_group_names', and no information about return values or error conditions.

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%, so the description must compensate. It describes only 6 of 9 parameters, missing the required 'instance_id'. The description for 'ports_security_group_names' is vague ('Port security groups mapping'). The note about project and region IDs is helpful but incomplete.

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 the action: 'Un-assign the security group to the server.' This distinguishes it from the sibling tool 'cloud_insts_assign_secgrp'. However, the phrasing could be more precise ('from the server' instead of 'to the server'), and it does not explicitly mention the instance resource.

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

Usage Guidelines3/5

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

The description provides one specific usage instruction: using NULL port_id to unassign from all ports. It does not discuss when to avoid this tool or compare it with alternatives beyond the implied opposite action.

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/G-Core/gcore-mcp-server'

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