Skip to main content
Glama

socialloop-mcp

by io.github.socialloopai
OverviewDiscussionsAdmin

Reject Community Event

reject_community_event
Destructive

Reject an event's request to be listed in a community you run (optional reason). Denies any Space booking request riding it — optionally suggest up to 5 alternative slots, each vetted against confirmed bookings (taken/invalid ones dropped + reported, never suggested). Restores the host's own payout if your community was the payout destination (unless tickets already sold). Requires community_id + event_id; you must be its creator/admin/moderator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNo
event_idYes
alternativesNo
community_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / alternatives
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "end_time": {
+        "maxLength": 64,
+        "minLength": 1,
+        "type": "string"
+      },
+      "note": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "space_id": {
+        "maxLength": 128,
+        "minLength": 1,
+        "type": "string"
+      },
+      "start_time": {
+        "maxLength": 64,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "space_id",
+      "start_time",
+      "end_time"
+    ],
+    "type": "object"
+  },
+  "maxItems": 5,
+  "type": "array"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses important behaviors beyond annotations: payout restoration (unless tickets sold), booking denial, and alternative slot vetting (dropping taken/invalid slots). Annotations only indicate destructiveness, so this adds significant context.

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?

The description is concise (5 sentences), front-loaded with the primary action, and each sentence adds essential detail without redundancy.

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?

The description covers main action, side effects, prerequisites, and alternatives logic. Lacks details on return value or error conditions, but is adequate for a destructive action with no output schema.

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?

With 0% schema coverage, the description explains key parameters: reason is optional, alternatives are vetted up to 5 slots. It adds meaning by clarifying the vetting process, though it omits detailed format for times and notes.

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 states the tool's verb ('Reject') and resource ('event request to be listed in a community'). It distinguishes from siblings like 'approve_community_event' by mentioning denial of bookings and payout restoration, which are unique to rejection.

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?

The description provides context for use: rejecting an event request in a community you run. It specifies prerequisites (must be creator/admin/moderator) and required parameters (community_id, event_id), but does not explicitly contrast with alternative actions like approval.

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

All socialloop-mcp 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