Skip to main content
Glama
Sign In

socialloop-mcp

by io.github.socialloopai
OverviewDiscussionsAdmin

Set Event Split Exception

set_event_split_exception
Idempotent

Adjust the split for ONE event only (setup 80/20, this event 90/10). Re-stamps the attached event immediately; sold tickets keep their terms; the standing setup is untouched; expires with the event. Community-set setups only. Requires community_id + member_uid + event_id + terms.

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>",
      "member_uid": "<member_uid>",
      "event_id": "<event_id>",
      "terms": "<terms>"
    },
    "name": "set_event_split_exception"
  }
}

Input Schema

NameRequiredDescriptionDefault
termsYes
event_idYes
member_uidYes
community_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses that sold tickets keep their terms, the standing setup is untouched, and the exception expires with the event. This adds context beyond annotations (idempotent, non-destructive), though it could note the result (e.g., success confirmation).

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 sentences pack essential information: the exception behavior and constraints. No redundancy or filler.

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 purpose, side effects, and constraints. Lacks output/return info but given no output schema, the behavioral description is reasonably complete for a mutation tool.

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?

With 0% schema description coverage, the description lists the required parameter names but provides no detail on the nested 'terms' structure (e.g., splits array, recipient fields). This leaves the agent to infer meaning from the schema alone, which is adequate but not enhanced.

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 it adjusts the split for ONE event only, with an example (80/20 to 90/10). This specific verb+resource combination distinguishes it from siblings like update_event or set_event_setup.

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 notes 'Community-set setups only' and lists required parameters, providing clear context. However, it does not explicitly state when NOT to use this tool or mention alternatives.

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