Skip to main content
Glama
Sign In
Sessionize

Sessionize

by labjp-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

getSessions

Retrieve session details including titles, descriptions, speakers, and schedules for Sessionize events to access conference information.

Instructions

List all sessions for a Sessionize event. Returns session titles, descriptions, speakers, and schedule information.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getSessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdNoSessionize event ID. Optional if SESSIONIZE_EVENT_ID is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the return data structure (session titles, descriptions, speakers, schedule information) but doesn't cover important behavioral aspects like pagination, rate limits, authentication requirements, or error conditions. The description is insufficient for a tool with no annotation coverage.

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, efficient sentence that clearly communicates the tool's purpose and return values without any wasted words. It's appropriately sized and front-loaded with essential information.

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?

For a simple read operation with one optional parameter and 100% schema coverage, the description is adequate but has gaps. Without annotations or output schema, it should ideally mention more about the return format (e.g., JSON structure, pagination) and operational constraints. It meets minimum viability but lacks completeness.

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 the single parameter completely. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3.

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 tool's purpose with a specific verb ('List') and resource ('sessions for a Sessionize event'), and specifies what information is returned. However, it doesn't explicitly differentiate from sibling tools like 'getSessionsBySpeaker' or 'findSession'.

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?

No guidance is provided about when to use this tool versus alternatives like 'getSessionsBySpeaker' or 'findSession'. The description only states what the tool does without indicating appropriate contexts or exclusions.

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

Deploy Server

Other Tools