Skip to main content
Glama
Sign In

QuintaDB

by com.quintadb
OverviewDiscussionsAdmin

delete_portal_group

Destructive

Delete a portal group together with its rights and members.

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": {
      "app_id": "<app_id>",
      "portal_id": "<portal_id>",
      "portal_group_id": "<portal_group_id>"
    },
    "name": "delete_portal_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesProject ID (from list_projects)
portal_idYesPortal ID (from list_portals or describe_project)
portal_group_idYesPortal group ID (from list_portal_groups or create_portal_group)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The description adds crucial behavioral detail—deleting members and rights along with the group itself—which is a specific scope not captured by the generic 'destructiveHint: true' annotation. This provides a comprehensive view of the operation's impact.

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?

It is a single, highly effective sentence. Every word is necessary, and the scope of the deletion is front-loaded, making it immediately clear to the agent what the tool achieves.

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 mutation tool with no output schema, the description is highly complete. It informs the agent exactly what will be removed (the group, its associated permissions, and its user list).

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 the parameters (app_id, portal_id, portal_group_id) are already well-defined. The description provides no additional meaning or constraints beyond the structural data provided in the schema.

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 resource (portal group) and the action (delete). Furthermore, it specifies the scope of the deletion, including its rights and members, making it more precise than a generic delete operation.

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?

While it doesn't explicitly compare itself to sibling tools, the description, combined with the destructive hint, clearly indicates the use case is irreversible removal of a container and its contents.

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

All QuintaDB toolsInspect
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