agendaforge

remove_session_speaker

Remove a speaker assignment from a session (the contact itself is not deleted). Depending on the organization's settings, this either executes immediately or files a proposal for approval; the response status field says which happened.

Input Schema

TableJSON Schema

Name	Required	Description
`org`	No	Organization slug. Only needed when you belong to multiple organizations; must be one returned by list_my_orgs.
`eventId`	Yes	Event id, as returned by list_events.
`contactId`	Yes	The contact id of the speaker to remove from the session.
`sessionId`	Yes	The session id.
`request_id`	Yes	Client-generated unique id for this write (e.g. a UUID). Retries with the same request_id return the original executed or proposed outcome instead of creating a duplicate. Never reuse a request_id for different arguments.

TDQS

A4.1/5.0

Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: the operation may execute immediately or file a proposal for approval depending on organization settings, and the response status field indicates which occurred. It also explicitly clarifies the non-destructive nature regarding the contact, which aligns with and enriches destructiveHint=false.

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 two sentences with no wasted words. It front-loads the primary action, adds a clarifying scope note, and then explains the variable behavior and response indicator. Every sentence contributes useful information.

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

Completeness5/5

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

For a write operation with no output schema, the description provides sufficient context: what is removed, what is not removed, the conditional approval behavior, and where to look in the response to understand the outcome. Combined with complete parameter schema descriptions, nothing critical is missing for an agent to invoke the tool correctly.

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?

Schema description coverage is 100%, so the schema already documents all parameters including eventId, contactId, sessionId, request_id, and org. The description adds no additional parameter-level meaning, which is acceptable at the baseline of 3 given the complete schema coverage.

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 states a specific verb and resource: 'Remove a speaker assignment from a session.' It also clarifies that the contact itself is not deleted, which distinguishes this from contact deletion or session deletion tools. This is clear and easily distinguishable from siblings like assign_speaker and delete_session.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives such as assign_speaker or delete_session. It implies its purpose through the action and resource, but offers no exclusions, prerequisites, or decision guidance for an agent comparing sibling tools.

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

All agendaforge tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation3/5

Most tools use distinct resource+action patterns and descriptions actively disambiguate similar cases, but several pairs remain easy to confuse: search vs semantic_search, send_email vs send_speaker_message, and the cluster around submission handling (decide_submission, set_submission_status, update_form_pipeline). The descriptions help, but the overlap is more than a single edge case.

Naming Consistency4/5

The set overwhelmingly follows verb_noun snake_case (create_session, update_sponsor, list_events) and prefixes are applied predictably. Minor deviations like semantic_search, bare search, check_in_attendee, and list_tracks_rooms break the pattern slightly, but they are still readable and not chaotic.

Tool Count1/5

55 tools is an extreme surface for an MCP server, even for a broad event-management platform, and it exceeds the 50+ threshold for severe over-scoping. Many tools are micro-variants of the same domain—multiple send_* tools and several submission-status tools—creating high selection burden for an agent.

Completeness3/5

The server covers a wide range of event, CRM, session, sponsor, form, and email workflows, but there are notable lifecycle gaps: events can be created and read but not updated or deleted, email templates have no update/delete path, and full form submission details and approval actions are absent. These are significant but not catastrophic because much of the core scheduling and contact workflow is covered.

Resources

Need Help?