Skip to main content
Glama
Sign In

esyURL

by io.github.esyurl
OverviewDiscussionsAdmin

Delete group

delete_group
Destructive

Delete a group. Its links are NOT deleted; they just stop being 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": {
      "groupId": "<groupId>"
    },
    "name": "delete_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesThe group id (groupId), as returned by create_group or list_groups

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations declare destructiveHint=true, so the destructive nature is already communicated. The description adds valuable behavioral context beyond the annotation: deleting a group does not delete its links, which instead stop being members. It does not cover permission requirements or whether the deletion is permanent, but it meaningfully clarifies the side effects.

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?

Two short sentences with no waste. The core action is front-loaded, and the clarifying consequence about links immediately follows.

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

Completeness4/5

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

For a single-parameter destructive tool with a fully documented schema and an existing destructiveHint annotation, the description is largely complete. It usefully clarifies link behavior but omits any note on permanence, permissions, or confirmation needs.

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 description coverage is 100%, and the single groupId parameter is fully documented in the schema as the id returned by create_group or list_groups. The description adds no further parameter semantics, so the baseline of 3 is appropriate.

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: delete a group. The second sentence further clarifies the scope by specifying that links are not deleted, which distinguishes this operation from link deletion or group update tools.

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 implies the tool is used when a group should be removed, but it does not explicitly state when to choose it over alternatives such as update_group or remove_link_from_group. The usage context is clear enough from the name and description, but explicit guidance is absent.

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

All esyURL 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