Skip to main content
Glama
Sign In
fulcradynamics

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Leave or Delete Group

leave_group
Destructive

Leave a Fulcra group to stop sharing its data types and receiving its shares; optionally delete a group you own and remove all members when explicitly requested.

Instructions

Leave a Fulcra group on the user's behalf, at their explicit request.

The user stops sharing the group's data types with its owner and stops receiving shares made to the group. With delete=true, instead permanently delete a group the user owns, removing every member; only when the user asks to delete it.

Input Schema

NameRequiredDescriptionDefault
deleteNoDelete the group for everyone (owner only) instead of leaving it.
group_idYesThe group, from `get_groups`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.18.7
    • addedInput schema / properties / delete
      Added value: +{
+  "default": false,
+  "description": "Delete the group for everyone (owner only) instead of leaving it.",
+  "type": "boolean"
+}
    • changedInput schema / properties / group_id / description
      Previous value: -"The group to leave, from `get_groups(subscribed_only=true)`."New value: +"The group, from `get_groups`."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Addedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations flag destructiveHint=true but say nothing specific; the description explains exactly what each mode does — leaving stops sharing data types with the owner and stops receiving group shares, while delete permanently removes every member and requires ownership. This is rich consequence disclosure well beyond the annotation flag.

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?

Front-loads the core action, then layers the behavioral detail and the delete caveat. Two tight paragraphs with zero filler; every sentence carries distinct information.

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, owner-sensitive two-parameter tool with no output schema, the description covers purpose, both operating modes, consequences, and the guardrail on deletion. An agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning to the `delete` flag beyond the schema: it removes every member, is permanent, requires ownership, and should only be used on explicit request. group_id is left to the schema, which already documents it.

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+resource ('Leave a Fulcra group') and immediately distinguishes the leave vs delete variants. An agent can tell this apart from join_group, create_group, and get_groups without opening a schema.

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?

Explicit usage context: 'at their explicit request' and 'only when the user asks to delete it' clearly constrain when the destructive delete variant should fire. It doesn't name sibling tools as alternatives, but the verb makes the join/create distinction self-evident.

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