Caly

List meeting sessions

list_booking_conferencing_sessions

Read-onlyIdempotent

List the video sessions (start, duration, participants) held for a booking.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bookingUid": "<bookingUid>"
    },
    "name": "list_booking_conferencing_sessions"
  }
}

Input Schema

Name	Required	Description	Default
`bookingUid`	Yes	Booking UID (a string like '2NtaeaVcKfpmSZ4CthFdfk'), as returned by list_bookings or create_booking.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world semantics, so the safety profile is fully handled. The description adds value by naming the returned shape (start, duration, participants), but does not say what happens when a booking has no sessions (empty list vs error) or whether results are ordered.

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?

A single efficient sentence with the verb and returned fields front-loaded; no filler.

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?

With no output schema, the description usefully summarizes the return fields, and the annotations cover safety. It is nearly complete for a simple read tool; only edge-case behavior (empty results) is missing.

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 coverage is 100% and the bookingUid parameter is documented in the schema with an example format and pointers to list_bookings/create_booking. The description adds nothing beyond this, so the baseline 3 is appropriate.

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?

States a specific verb ('List') and resource ('video sessions... held for a booking') and names the returned fields (start, duration, participants). It is clear on its own, but does not explicitly differentiate from nearby siblings like list_booking_recordings or list_booking_transcripts, which an agent might confuse for 'sessions' of another kind.

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 on when to use this versus the recording/transcript/attendee listing siblings, and no prerequisites stated (e.g. booking must have conferencing configured). The context is implied by 'held for a booking' but no alternative or exclusion is named.

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

All Caly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?