unassign_event_from_spaceAs a community you run, UNASSIGN an event from its venue Space here — frees the Space's calendar slot (recorded admin_released) and clears the event's venue link; the event keeps its listing and venue text. Idempotent — an event with no active booking here changes nothing. Creator/admin/moderator. Requires community_id + event_id.
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | ||
| community_id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description claims idempotency ('Idempotent — an event with no active booking here changes nothing'), but annotations set idempotentHint to false, creating a contradiction. This undermines trust.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose, includes idempotency and auth. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Explains effect on slot and venue link, but lacks return value description and examples. Given no output schema, more detail on response would be helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% parameter description coverage. Description only repeats required params without adding meaning (e.g., format, examples). Does not compensate for lack of schema details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool unassigns an event from a space, frees the slot, and clears the venue link, distinguishing it from sibling assign_event_to_space.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Specifies idempotency, required roles (creator/admin/moderator), and required parameters. Lacks explicit when-not-to-use or alternative tool names, but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.