Skip to main content
Glama
Sign In

socialloop-mcp

by io.github.socialloopai
OverviewDiscussionsAdmin

Approve Community Event

approve_community_event

Approve a pending event submission in a community you run — listing, pre-consented deal terms, and any venue Space booking confirm in ONE atomic action. REFUSES payout-routing submissions (money approvals happen in the studio — link provided). A slot taken meanwhile aborts the whole approval with the conflict named. Requires community_id + event_id; creator/admin/moderator.

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": {
      "community_id": "<community_id>",
      "event_id": "<event_id>"
    },
    "name": "approve_community_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
assign_spaceNo
community_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / assign_space
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "end_time": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "space_id": {
+      "maxLength": 128,
+      "minLength": 1,
+      "type": "string"
+    },
+    "start_time": {
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "space_id",
+    "start_time",
+    "end_time"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

The description discloses atomic behavior, refusal of payout submissions, and slot conflict handling. Since annotations (readOnlyHint=false, etc.) provide no safety profile, the description adds necessary behavioral context. It could mention side effects like notifications or event state updates.

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?

The description is concise with two sentences, front-loading the main action and following with constraints. It avoids unnecessary detail, though the first sentence is long and could be split for readability.

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

Completeness3/5

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

With no output schema, missing return value information limits completeness. The description covers purpose, constraints, and conflict behavior but lacks success response details and full explanation of nested parameters like assign_space.

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?

The description highlights required parameters community_id and event_id, and implies the assign_space object handles venue booking. However, schema coverage is 0% and the description does not explain each parameter in detail, leaving some ambiguity for the agent.

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 approves a pending event submission in an atomic action, covering listing, deal terms, and space booking. It distinguishes from sibling tools like reject_community_event and list_pending_community_events, and specifies the verb and resource exactly.

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 explicit when-not-to-use guidance (refuses payout-routing submissions) and hints at atomicity and conflict handling. It mentions required roles (creator/admin/moderator) but does not compare directly with alternatives like accept_deal or submit_event_to_community.

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