agendaforge

create_session_from_submission

Turn an approved form submission into a session. 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.
`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.
`submissionId`	Yes	The submission id.

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses the conditional behavior beyond the annotations: execution may happen immediately or result in a proposal for approval, and the response status indicates which. This is valuable behavioral context that readOnlyHint=false and destructiveHint=false alone do not provide.

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, both information-dense and front-loaded with the core purpose. No filler or repetition of schema content.

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 the main operational nuance (immediate vs. proposal) and points to the response status field. It leaves exact status values and error behavior unspecified, but with 100% parameter schema coverage and no output schema required, it is sufficiently complete for tool selection and invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning by specifying that the submission must be approved, which clarifies submissionId beyond the schema's bare description. It also informs the agent about a response status field, helping interpret output even without an output schema.

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 uses a specific verb and resource: 'Turn an approved form submission into a session.' This clearly distinguishes the tool from generic create_session and schedule_session by tying it to an existing approved submission.

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 gives clear context about when this tool applies: only for approved form submissions, with behavior depending on organization settings. It does not explicitly name alternatives like create_session, but the approved-submission prerequisite makes the selection clear enough.

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?