socialloop-mcp

Add Task

add_task

Add a production task to a live event — title, priority, and phase (pre_production/build/event/strike/post). Requires event_id + title; you must be a host.

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": {
      "event_id": "<event_id>",
      "title": "<title>"
    },
    "name": "add_task"
  }
}

Input Schema

Name	Required	Description	Default
`phase`	No
`title`	Yes
`event_id`	Yes
`priority`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 3, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations indicate this is a write operation (non-readOnly) and not destructive or idempotent. The description adds that the user must be a host, which is useful. However, it does not disclose side effects, such as what happens if a task with the same title already exists, or any rate limits.

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 a single, well-structured sentence that conveys the core functionality and constraints without unnecessary words. It is front-loaded and efficient.

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?

Given the tool has 4 parameters, 2 enums, no output schema, and moderate complexity, the description covers basic requirements but lacks explanation of return values, error conditions, or behavior with optional parameters. It is adequate but not thorough.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'title, priority, and phase' but does not explain enum values (e.g., what 'explore' priority means) or provide any additional context for the event_id parameter. The description adds minimal meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Add' and the resource 'production task to a live event', and lists key parameters. However, it does not differentiate from sibling tools like add_production_item or add_schedule_item, which could cause confusion.

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 states prerequisites ('requires event_id + title; you must be a host') but does not provide guidance on when to use this tool vs alternatives or when not to use it. Usage context is implied but not explicit.

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

All socialloop-mcp tools Inspect

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.