Skip to main content
Glama

skycloak_delete_openfga_instance

Destructive

Permanently delete an OpenFGA instance and its deployment, route, and database, removing authorization data irreversibly. Set confirm=true to start the asynchronous deletion.

Instructions

Permanently delete an OpenFGA instance with its deployment, route and database. The authorization data in it cannot be recovered. Works without OpenFGA access. Removal is asynchronous: the instance shows 'deleting' until it leaves the list. Set confirm=true to proceed.

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": {
      "cluster_id": "<cluster_id>",
      "instance_id": "<instance_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_openfga_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm permanent, irreversible deletion of the instance and its authorization data
cluster_idYesthe cluster the instance belongs to
instance_idYesthe OpenFGA instance ID to delete

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already mark this destructive and non-idempotent, but the description adds substantive behavior beyond them: irreversible loss of authorization data, the exact resources removed, that the call succeeds without OpenFGA connectivity, and that removal is asynchronous with a transient 'deleting' state. Those are the details an agent needs to reason about side effects and follow-up polling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short sentences, front-loaded with the destructive action and its scope, then prerequisites and async behavior. Slight redundancy in restating the confirm=true requirement already spelled out in the schema keeps it from a 5.

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

Completeness5/5

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

For a destructive, cascading, asynchronous deletion, the description covers scope, irreversibility, the confirmation gate, connectivity requirements, and the post-call state. An output schema exists, so no return-value explanation is needed and nothing material is missing.

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%, so cluster_id, instance_id and confirm are already fully documented. The description echoes the confirm gate but adds no syntax, format, or edge-case meaning beyond the schema, which is the expected baseline.

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?

States a specific verb and resource ('Permanently delete an OpenFGA instance') and goes further to enumerate the cascade ('with its deployment, route and database'), so an agent knows exactly what is destroyed. It is clearly distinguishable from create/get/list siblings in the same OpenFGA family.

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?

Gives a real precondition ('Works without OpenFGA access') and an explicit gate ('Set confirm=true to proceed'), which is clear context for when/how to call. It stops short of naming a when-not condition or an alternative tool, so it is not a full 5.

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