agendaforge

list_sessions

Read-only

List the event's sessions (up to 200): title, status, time, room, track, and speaker names. Filter by status, track, or scheduled/unscheduled.

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.
`status`	No	Filter by session status (e.g. proposed, accepted, confirmed, rejected).
`eventId`	Yes	Event id, as returned by list_events.
`trackId`	No	Filter to one track (id from list_sessions rows or the event overview).
`scheduled`	No	true → only sessions with a scheduled time; false → only unscheduled.

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds a meaningful behavioral detail: a hard cap of 200 returned sessions, and the available filter dimensions.

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, front-loaded with the core listing behavior and returned fields, then the filter options. Every word earns its place.

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 simple read-only list tool with no output schema, the description is complete: it names the returned fields, the 200-row cap, and all filter dimensions. Combined with the well-documented schema, an agent has everything needed to invoke it 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%, with clear descriptions for all five parameters including eventId, trackId, status, scheduled, and org. The description lightly reinforces the filter options but adds no syntax or format details beyond the 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?

States a specific verb and resource: 'List the event's sessions' with concrete returned fields and filter options. The plural scope clearly distinguishes it from siblings like get_session and list_submissions.

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?

Clear context is provided: use it to get a filtered read-only overview of sessions for an event, with status, track, and scheduling filters. It doesn't explicitly name alternatives or exclusions, but the intended use is unmistakable.

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?